122882434 SAP Extended Warehouse Management SAP EWM

ADDON.SPL_SCM_WM

SAP Extended Warehouse Management (SAP EWM)

Release 510

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

Description

Example text

Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, graphic titles, and table titles.

EXAMPLE TEXT

Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text

Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.



Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT

Keys on the keyboard, for example, F2 or ENTER.

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 Section

Storage Sec. Activity Area Storage Bin

Storage Bin

Quant

Quant

The warehouse structure in warehouse management is divided hierarchically and consists of the following elements: ●

Warehouse number In EWM, you can manage an entire physical warehouse complex using a single warehouse number.

●

Storage type You can define the individual warehouse facilities or warehouses that make up the warehouse complex, using their technical, spatial, and organizational characteristics as storage types.

●

Storage section Each storage type is divided into storage sections. All storage bins with specific common attributes belong to one storage section, for example, storage bins for fastmoving items that are close to the goods issue zone.

SAP Extended Warehouse Management (SAP EWM)

510

21

SAP Online Help ●

20.07.2007

Storage bin Each storage type and storage section consists of a selection of storage compartments that are called storage bins in EWM. The coordinates of the storage bin tell you the exact position in the warehouse, where you can store products.

●

Quant The quant is used for inventory management of a product in a storage bin.

●

Activity area The activity area is a logical grouping of storage bins. It can refer to a storage bin, or can concatenate bins from several storage types. You can either assign storage bins manually to the activity areas, or if there is a 1:1 relationship between storage type and activity area, you can have the system generate the assignment.

To map the structure of your physical warehouse in the system, you define the warehouse structures in EWM in Customizing. We recommend that you use the following sequence when configuring the warehouse structure in the system. In the Implementation Guide (IMG) for EWM, choose Extended Warehouse Management → Master Data → ... ...

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

SAP Extended Warehouse Management (SAP EWM)

510

22

SAP Online Help

20.07.2007

Warehouse Number Definition In Extended Warehouse Management (EWM), you combine an entire physical warehouse under one warehouse number. You can use the warehouse number to manage several storage facilities, which together form the complete warehouse complex.

Use The organizational and physical attributes of a warehouse complex are collected together under the warehouse number. For example, the weight unit, volume unit, and time unit are defined at warehouse number level. You can also define determination procedures for palletization data and packaging specifications [Seite 494] here. You should not change these settings at a later time.

We recommend using one warehouse number for each group of storage areas or buildings (warehousing complex) in the same geographical area. If your warehousing facilities are located in different cities or are physically separated by a longer distance, it is appropriate to assign a separate warehouse number to each warehouse complex. For more information about defining a warehouse number, see the Implementation Guide (IMG) for Extended Warehouse Management under Master Data → Define Warehouse Number Control. You must make a one-time assignment between the warehouse number and a supply chain unit [Seite 53] with the business character Warehouse as a continuous setting. For more information, see the IMG for Extended Warehouse Management under Master Data → Assign Warehouse Numbers. Note, however, that you must make this assignment in the production system. For this reason, you should make this setting from the SAP menu under Extended Warehouse Management → Settings → Assignments: Warehouse Numbers/Business Partners. The supply chain unit contains essential information, such as country, region, and time zone. The system uses the time zone for the warehouse number when displaying all date and time fields. You can create a supply chain unit in the SAP menu under Extended Warehouse Management → Master Data → Maintain Supply Chain Unit.

As soon as you actively use a warehouse number, for example because you have already created a warehouse number product, you should no longer change the assignment of the supply chain unit to the warehouse number. Doing so can result in follow-on errors.

Example The warehouse for company XYZ includes the following facilities: ●

Goods receipt area

●

Goods issue area

●

Hall with high rack shelves

●

Bulk storage area

●

Activity areas of category Picking with Fixed Bins

SAP Extended Warehouse Management (SAP EWM)

510

23

SAP Online Help ●

20.07.2007

Storage space outdoors for special substances

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

SAP Extended Warehouse Management (SAP EWM)

510

24

SAP Online Help

20.07.2007

Storage Type Definition A storage type is a storage space, storage facility, or storage zone, which you define for a warehouse number in Extended Warehouse Management (EWM). The storage type is a physical or logical subdivision of a warehouse complex, which is characterized by its warehouse technologies, space required, organizational form, or function. A storage type consists of one or more storage bins. You can define the following commonly-used physical storage types in EWM: ●

Bulk storage area

●

General storage area

●

High rack storage area

●

Fixed bin storage area

●

Rack storage area

Use The storage types form the warehouse complex and can be located in one or more buildings. You manage all storage types under a single warehouse number. The standard system for EWM comes configured with several complete storage types that you can use straightaway. These include: ●

High rack storage area

●

Bulk storage area

●

Fixed bin storage area

●

General storage area

●

Pallet storage area

These storage types have all been defined with different control indicators for putaway and picking.

You can use the standard storage types as the basis for your individual settings, or you can create your own storage types to meet the special requirements of your company. Defining Control Indicators in the Storage Type At storage type level, you must specify the control indicators that control the material flow (putaway and picking) in each storage type. These include the control indicators for: ●

Putaway

●

Stock removal (picking)

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

510

25

SAP Online Help

20.07.2007

You can only activate or deactivate the level of the available quantities and handling unit management requirement, if there are no stocks present within a storage type. We recommend that you only change the capacity check for a storage type if no more stocks are present within the storage type. Particular care should be taken if you subsequently change the putaway behavior for putaway. In the storage type, there are indicators that you can override in the warehouse process category. This means that specific functions, such as the confirmation requirements for putaway and picking or the option for posting changes to the same storage bin, are valid for specific storage types, but are not valid for a specific posting. For more information about changing the predefined storage types or creating new storage types, see the Implementation Guide (IMG) for EWM under Extended Warehouse Management → Master Data → Define Storage Type.

Example You can define several storage types for each warehouse number. The following figure shows five storage types that are assigned to a warehouse number:

Warehouse Number 0001 Storage Type 9020

Storage Type 0010

GR Area Goods Receipt

High Rack Storage Area Storage Type 0040

Block Storage Area Storage Type 9100

Storage Type 0050

GI Area Fixed Bin Storage Area Goods Issue

SAP Extended Warehouse Management (SAP EWM)

510

26

SAP Online Help

20.07.2007

Activity Area Definition Logical section of the warehouse that groups storage bins based on defined warehouse activities. Examples of activity areas include: ●

Putaway [Seite 300]

●

Picking [Seite 322]

●

Inventory [Seite 667]

Use You use activity areas to provide logical subdivisions in your warehouse. In these activity areas, different warehouse workers execute certain warehouse activities, such as putaway or picking. You create activity-dependent bin sortings within an activity area. Extended Warehouse Management (EWM) uses these bin sortings to optimize the execution of warehouse tasks.

Structure An activity area consists of one or more assigned storage bins. You can define the assigned storage bins using the following attributes: ●

Aisle

●

Stack

●

Level

●

Bin subdivision

●

Depth

●

Information about the storage type

●

Any assigned deconsolidation groups

You can sort these storage bins into any sequence you want, and assign as many activities to them as you require. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Master Data → Activity Areas → Assign Storage Bins to Activity Areas and Define Sort Sequence for Activity Area.

To be able to work with activity areas, you have to generate the bin sorting. On the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Storage Bin → Sort Storage Bins. You can generate activity areas from storage types in Customizing. For more information, see the IMG for EWM under Master Data → Activity Area → Generate Activity Area from Storage Type. In this case, the activity area has the same storage bins as the storage type.

SAP Extended Warehouse Management (SAP EWM)

510

27

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

28

SAP Online Help

20.07.2007

Storage Section Definition In Extended Warehouse Management (EWM), a storage section is an organizational subdivision of a storage type, which joins together storage bins with similar attributes for the purpose of putaway. The criteria for joining these bins together can be defined in any way, for example, heavy parts, bulky parts, fast-moving items, slow-moving items.

Use You can use the storage section as an organizational aid for putting away goods in the warehouse. When you use storage types and storage sections, you must define the organizational aims clearly. The physical location is the main organizational factor. It is not absolutely mandatory that you subdivide a storage type into two or more storage sections. However, you must create at least one storage section for each storage type.

You can only define control parameters and control values in the storage type. For information on how to define a storage section for a storage type, see the Implementation Guide (IMG) for Extended Warehouse Management under Master Data → Define Storage Sections.

Example High rack storage areas frequently consist of many storage bins that vary in size. For example, in many such storage areas, the bins in the lower level are larger for especially large and heavy parts, while those in the upper levels are smaller. The following figure shows a high-rack storage area divided into two storage sections. You use the front storage section for fast-moving items, and the back storage section for slowmoving items. Storage bin 02-02-03

Bin type

High bins

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

Storage section

SAP Extended Warehouse Management (SAP EWM)

510

29

SAP Online Help

20.07.2007

Storage Bin Definition A storage type consists of a selection of storage spaces, which are called storage bins in Extended Warehouse Management (EWM). The storage bin is the smallest spatial unit in a warehouse. Therefore, the storage bin represents the exact position in the warehouse where products are and/or can be stored. Since the address of a storage bin is frequently derived from a coordinate system, a storage bin is often referred to as a coordinate. For example, the coordinate 01-02-03 could be a storage bin in aisle 1, stack 2, and level 3.

Use To each storage bin, you assign the warehouse number in which the storage bin is located. You just also assign a storage type [Seite 25] and storage section [Seite 29] to each storage bin. You can also define the following additional attributes for a storage bin: ●

Maximum weight

●

Total capacity

●

Fire-containment section

●

Storage bin type (for example, for large or small pallets) In some putaway strategies, the storage bin type plays an important role during optimization of the automatic search for a storage bin, in connection with the pallet type. For example, you can define the putaway strategy in such a way that you put away large industrial pallets into special large bins, and smaller pallets into small bins.

For information about defining storage bins, see the Implementation Guide (IMG) for Extended Warehouse Management under Master Data → Storage Bins.

Structure You can use any combination of letters and numbers for storage bin coordinates. However, you should ensure that you orient the parts of the structure to the indicators defined for the warehouse for aisle, stack, level, and so on.

SAP Extended Warehouse Management (SAP EWM)

510

30

SAP Online Help

20.07.2007

Quant Definition Stock of a specific product with the same characteristics in one storage bin [Seite 30], resource [Seite 752], and transportation unit [Seite 613]. The system manages different batches of a product as different quants. You can increase the quantity of a quant by adding to the existing stock. Quants can only be created and deleted using movements.

Use Quants are used to manage stocks at storage bin level, resources, and transportation units. When you put a product away into an empty bin in Extended Warehouse Management (EWM), the system generates a quant in this storage bin. When you remove the quantity from storage, the system automatically deletes the quant. In the quant record, the system manages the data for the products collected together in the quant. This data includes: ●

Quant identification

●

Number

●

Batch number

●

Stock category type

●

Stock category

●

Stock usage

SAP Extended Warehouse Management (SAP EWM)

510

31

SAP Online Help

20.07.2007

Door Definition Location in the warehouse where the goods arrive at or leave the warehouse. The door is an organizational unit that you assign to the warehouse number. Vehicles [Seite 612] and their transportation units (TUs) [Seite 613] drive up to the doors of a warehouse to load or unload goods there. The doors are in close proximity to the relevant staging areas [Seite 33].

Use To control putaway and stock removal processes in your warehouse, you can define doors and staging areas within a warehouse number. You can assign various functions to a door: ●

Inbound

●

Outbound

●

Inbound and outbound

In delivery processing, the system uses determination rules to determine the following for each delivery item: ●

Staging area groups

●

Staging areas

●

Staging bays

●

Doors

The determination rules are influenced by the possible assignments that you have defined in Customizing between doors and staging areas as well as between doors and staging area/door determination groups. The system updates the delivery at item level with the values that it finds. You define doors in Customizing for Extended Warehouse Management (EWM) under Master Data → Warehouse Door → Define Warehouse Door. You assign staging areas and staging area/door determination groups to your doors under Master Data → Warehouse Door.

Structure You assign each door to a storage bin that you can use to post goods receipts or goods issues. You assign this storage bin to a storage type with the storage type role F. You can also assign doors to supply chain units [Seite 53] to control authorization checks. You can also assign doors to yard bins (see Yard Management [Seite 619]). See also: Staging Area and Door Determination [Seite 615]

SAP Extended Warehouse Management (SAP EWM)

510

32

SAP Online Help

20.07.2007

Staging Area Definition Organizational unit that is assigned hierarchically to the warehouse number and that is used to organize the flow of goods in the warehouse.

Use Staging areas are used for the interim storage of goods in the warehouse. They are located in close proximity to the doors [Seite 32] assigned to them. You can define staging areas for different purposes and even simultaneously for multiple purposes: ●

Goods receipt Interim storage of unloaded goods until they are put away

●

Goods issue Interim storage of picked goods until they are loaded

In Customizing, you define staging areas and assign the staging areas to the relevant doors. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Master Data → Staging Areas → Define Staging Areas and Master Data → Warehouse Door → Assign Staging Area to Warehouse Door.

Structure You can group multiple staging areas into staging area groups. The staging area group corresponds to a storage type (storage type role “D”), while the staging area corresponds to a storage section. You can divide each staging area into one or more storage bins. You need multiple storage bins, for example, if you want to define a loading sequence. See also: Staging Area and Door Determination [Seite 615]

SAP Extended Warehouse Management (SAP EWM)

510

33

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

34

SAP Online Help

20.07.2007

Work Center Definition The work center is a physical unit in the warehouse, in which you can perform warehouse activities such as packing, distribution, or weighing.

Use You can use the work center in the following processes: ●

Packing

●

Deconsolidation

●

Counting

●

Quality Inspection

Extended Warehouse Management (EWM) contains the following transaction types for the work center: ●

Packing - General This transaction type is for all general repacking transactions.

●

Deconsolidation This transaction type is for distributing mixed handling units (HUs) into HUs for nonmixed deconsolidation groups.

●

Quality Inspection and Count This transaction type is for entering count and inspection results, and for confirming inspection results.

●

Packing in the Staging Area This transaction type is for packing together HUs according to the criterion Stop on Route.

You must assign each work center to a warehouse number, storage type, and storage bin. Note that you can only use storage types that have the storage type role ‘Work Center’ (E), ‘Pick Point’ (B), or ‘Identification and Pick Point’ (C). You can configure more than once work center for each storage type in the system. You can assign an inbound and outbound section to each work section. For more information about setting up work centers, see the Implementation Guide (IMG) for EWM under Extended Warehouse Management → Master Data → Work Center.

Example The following example shows you various options, for example, on how a work center for deconsolidation can be structured: Work center 1 represents the deconsolidation work center, which has no inbound section and no outbound section. Work center 2 represents the deconsolidation work center, which has an outbound section but no inbound section. Work center 3 represents the deconsolidation work center, which has both an inbound section and an outbound section.

SAP Extended Warehouse Management (SAP EWM)

510

35

SAP Online Help

Work Center WC1

20.07.2007

Work Center WC2

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

WC1

WC2

WC3I-02

WC3

Inb. Section Work Center

Work Center

0001

0001

WC2O-01WC2O-02WC2O-03

Storage Type 8000

WC2O

0001

Outb. Section Work Center

WC3O-01 WC3O-02WC3O-03

Storage Bin

WC3O

You can also join work centers together into work center groups. This means that you can send individual products or HUs to a work center group, which corresponds to a storage section. In the above example, this would be a warehouse task to storage section 0001. The system only determines the final storage bin, and thus the work center, when you confirm the warehouse task.

SAP Extended Warehouse Management (SAP EWM)

510

36

SAP Online Help

20.07.2007

Resource Definition A resource is an entity representing a user or equipment, which can execute work in the warehouse.

Use A resource can log on to a radio frequency (RF) or non-RF environment. Once the resource is logged on to the system, it can receive work for execution, and can be tracked and displayed in the warehouse management monitor [Seite 878].

For more information about logging on to an RF environment, see Logon [Seite 790]. For more information about how resources receive work, see Assignment of Warehouse Order to Resource [Seite 755].

Structure A resource belongs to a resource type [Seite 753] and resource group [Seite 754].

You define a resource in the transaction for resource maintenance. To do so on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Resource Management → /SCWM/RSRC – Maintain Resource. Alternatively you can define a resource by using the warehouse management monitor (method [Seite 882] Maint. Resource).

SAP Extended Warehouse Management (SAP EWM)

510

37

SAP Online Help

20.07.2007

Resource Type Definition A resource type is a grouping of resources with similar technical or physical qualifications.

Use The resource type determines the following for its corresponding resources [Seite 752]: ●

Horizontal velocity The velocity of a resource can influence the LSD of a warehouse order (WO). For more information, see Latest Starting Date (LSD) [Seite 760].

●

Applicability of position management For more information, see Position Management [Seite 795].

●

Qualifications and preferences (reflected by priority values) regarding bin access types [Extern] and HU type groups [Extern] The qualifications and priority values influence which WOs are selected for a resource requesting work. For more information, see Warehouse Order Selection [Seite 757].

You define resource types, and assign to them qualifications, in Customizing for Extended Warehouse Management → Cross-Process Settings → Resource Management → Define Resource Types. You maintain the qualification priority values using the execution priority maintenance transaction, accessed on the SAP Easy Access screen (Extended Warehouse Management → Master Data → Resource Management → /SCWM/EXECPR - Maintain Execution Priorities).

SAP Extended Warehouse Management (SAP EWM)

510

38

SAP Online Help

20.07.2007

Resource Group Definition A resource group is a grouping of resources for queue [Seite 764] assignment purposes.

Use The resource group determines the sequence of allowed queues for its corresponding resources [Seite 752], which can influence which WOs are selected for a resource. For more information, see Warehouse Order Selection [Seite 757].

You assign/unassign a resource group to/from a queue using the queue sequence for resource group transaction, accessed on the SAP Easy Access screen (Extended Warehouse Management → Master Data → Resource Management → /SCWM/QSEQ - Maintain Queue Sequence for Resource Group), or from the warehouse management monitor [Seite 878] (Assign Queue/Unassign Queue methods [Seite 882]).

SAP Extended Warehouse Management (SAP EWM)

510

39

SAP Online Help

20.07.2007

Warehouse Product Definition Warehouse-number-dependent view of the product master data. The warehouse product comprises all the properties of a product that relate to its storage in a certain warehouse within the framework of Extended Warehouse Management (EWM), such as the putaway control indicator.

Use You need the warehouse product if you wish to use a product whose global data you have already maintained in the product master in EWM. You can create or change a warehouse product via the SAP menu under Extended Warehouse Management → Master Data → Maintain Warehouse Product. Entry of the warehouse number [Seite 23] and the ‘party entitled to dispose’ is mandatory, because the warehouse-number-dependent data pertaining to the warehouse product applies only to this warehouse number and this party.

Structure The warehouse-number-dependent data on the warehouse product can be found on the following tab pages in the maintenance function for warehouse products: ●

Warehouse data Here you maintain data on the warehouse in which the product is stored.

●

Slotting For more information, see Slotting [Seite 277].

●

Storage type data Here you maintain data on the type of facility in which the product is stored. For more information, see Storage Type [Seite 25].

Integration Global, warehouse-number-independent data pertaining to the storage of the product can be found on the Storage tab page. This tab page is also displayed in product master maintenance. The following warehouse-number-independent data on the storage of a product is adopted in EWM from the ERP system. ●

Handling unit types

●

Warehouse product group

●

Warehouse storage condition

●

Warehouse handling indicator

●

Serial number profiles

●

Quality inspection groups

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

SAP Extended Warehouse Management (SAP EWM)

510

40

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

41

SAP Online Help

20.07.2007

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

Substance.

SAP Extended Warehouse Management (SAP EWM)

510

42

SAP Online Help

20.07.2007

Packaging Specification Definition A packaging specification is master data. The packaging specification defines all the necessary packing levels for a product in order, for example, to put away or transport the product. For a product, a packaging specification mainly describes in which quantities you can pack the product into which packaging materials in which sequence.

Use ●

In printed form, a packaging specification is a set of instructions for the employee in the warehouse. More specifically, the work steps that you enter in a packaging specification are intended as information for the employee. In this way you can, for example, give the employee exact instructions as to where to place the label on a box, or how a product should be stacked onto a pallet.

●

The system can determine packaging specifications during various processes (see below). Processes that determine packaging specifications use only parts or specific attributes from the packaging specification.

Structure Header

Product

Contents

OR or

Packaging specification Level 1

●

EG 1

Element 1

Pack. mat.

Work step

Element 2

Pack. mat.

Work step

Level 2

EG 2

Element 1

Pack. mat.

Work step

Level n

EG n

Element 1

Pack. mat.

Work step

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

SAP Extended Warehouse Management (SAP EWM)

510

43

SAP Online Help ●

20.07.2007

Contents A packaging specification contains a product. However, some packaging specifications contain more than one product, or refer to other packaging specifications.

●

Level You can map various packing levels in a packaging specification. Each level contains a target quantity, which defines how many times you can pack the previous level into this level.

●

Element group For each level there is exactly one element group. However, you can reuse element groups in several packaging specifications.

●

Elements Elements consist of a packaging material and/or a work step.

●

Step A text with an identification, which you can use in one or more packaging specifications.

●

Packaging material A product that is defined with a packaging material type in the product master.

Example for a Packaging Specification and Its Structure: Header: Name: PS1, Status: New Contents: product A, 1 piece Level 1: Target quantity one, element group EG1 Element group EG1: ●

Element E1: packaging material ‘Small box’, work step ‘Place 1 piece upright in each box’

●

Element E2: additional packaging material ‘Label’, work step ‘Place label on upper left’

Level 2: Target quantity 50, shift quantity 10, element group EG2 Element group EG2: ●

Element E3: packaging material ‘Pallet’, work step ‘Place boxes layer by layer onto pallet’

Integration The following figure shows which processes use the packaging specification, and using which components:

SAP Extended Warehouse Management (SAP EWM)

510

44

SAP Online Help

20.07.2007

Processes for the Packaging Specification

Inb. delivery/ASN

Putaway-WT Stock-removal-WT Slotting

Automatic packing

Palletization

ICH

Whse-int. processes

Pick-HU proposal

ATP sourcing

Warehouse order

EWM

MM deployment

Rounding rules

APO

Packaging Specification iPPE

Cond. technique

In both the Inventory Collaboration Hub (ICH) and in Extended Warehouse Management (EWM), you can use the same packaging specification for an inbound delivery or an ASN that you then use for the Automatic Packing [Seite 510] process.

Example Palletization data in EWM In your warehouse, you put away product A onto pallets for 50 pieces. Create a packaging specification with a level that contains the main packaging material Pallet and the contents Product A. For this level, enter the target quantity 50. In the process ‘Putaway’ for the inbound delivery, the system splits the quantity in the inbound delivery across multiple warehouse tasks, due to this packaging specification. For example, if a quantity of 100 pieces is delivered, then the system creates two warehouse tasks for 50 pieces.

Functions of the Packaging Specification The following functions are possible for packaging specifications: ●

Create, copy, and activate (see also: Creation of Packaging Specifications [Seite 497])

●

Determine (see also: Packaging Specification Determination [Seite 499])

●

in mehrere Systeme verteilen.

SAP Extended Warehouse Management (SAP EWM)

510

45

SAP Online Help

20.07.2007

Route Definition Sequence of legs that are connected by transshipment locations [Extern].

Use The route represents a framework or corridor that comprises a multitude of trips, in other words, possible concrete itineraries. The system uses routes to determine trips in route determination [Seite 638]. The following figure shows a route with three legs that are connected by the transshipment locations P and M. It also shows a (red) trip for the case where all stop-offs in the middle leg are optional and a (blue) trip for the case where these stop-offs are mandatory. Transshipment Location P

Destination Location Z Le g

Start Location A

Transshipment Location M

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

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

Structure Leg A leg is assigned uniquely to a route, in other words, it cannot be part of multiple routes. You define legs as a sequence of stops. Each stop is a supply chain unit (SCU) [Seite 53], in other words, a location or zone [Seite 646]. The stops that connect two consecutive legs must be locations. By specifying whether the stop-offs are optional or mandatory, you define which locations the carrier is to serve in which order. You assign exactly one means of transport to each leg. In most cases, adjacent legs of a route have different means of transport. However, it might also be necessary to change legs due to various properties of the legs. Nonetheless, in most cases, the legs of a route represent its unimodal parts. Stop At stop level, you can assign a mode of transport for foreign trade to each location. The system then takes into account this mode of transport for outbound shipments in the case of exports. The value that represents this mode of transport is dependent on the country in which the location lies. The system does not check if the mode of transport semantically matches the means of transport used for the leg of this location. Since, in most cases, the system cannot define a unique country for zones, it does not permit you to define a mode of transport for such stops.

SAP Extended Warehouse Management (SAP EWM)

510

46

SAP Online Help

20.07.2007

In static route determination, the system determines the mode of transport for foreign trade for outbound shipments (trips) in the following sequence: 1. Country of first location 2. Part of the location sequence of the trip that runs from the first location within this country 3. The first location in this part of the location sequence when going backward that is a stop along the leg and for which a mode of transport for foreign trade was defined, in other words, the location that lies closest to the border. Carrier Assignment You can assign as many different carriers as you want to your means of transport or any of its subordinate means of transport for the leg. You can specify whether dangerous goods can be transported for each such combination of leg, means of transport, and carrier. In static route determination, the system defines the carrier for a trip as the carrier for the first leg who can transport dangerous goods, if required, and for which you have defined the lowest costs for transportation along this leg in the carrier profile. Departure Calendar Assignment You can define a departure calendar for the leg. If the departures for a specific request type do not correspond with the departure calendar for the leg, you can also define a specific departure calendar for this request type. The system takes into account departure calendars when scheduling [Seite 656] a trip for both the start location of the request and for each transshipment location served. Validity and Restrictions You can restrict the validity of a route by specifying the following: ●

A validity period that the system compares with the cutoff time of a single request.

●

Permitted shipping conditions that the system compares with the shipping conditions of a single request.

●

Permitted request types that the system compares with the request type of a single request. You can specify permitted request types at the header level of the route and for each stop within the leg (customer, for example). The request types at stop level must be part of the request types that you specify at header level. Request types at stop level have a higher priority than those at header level. Accordingly, the request types at header level are valid for those stops for which you have not defined separate request types.

●

Permitted transportation groups that the system compares with the transportation groups of the products in a single request.

●

Weight limits for single and collective requests that the system compares with the total weight of the products in the single request or in multiple combined requests You can also specify weight limits for single and collective requests for each stop within a leg. These limits overwrite the relevant limits that you specify for the route at header level.

●

Volume limits for single and collective requests that the system compares with the total volume of the products in the single request or in multiple combined requests You can also specify volume limits for single and collective requests for each stop within a leg. These limits overwrite the relevant limits that you specify for the route at header level.

●

Dimension limits (length, width, and height)

SAP Extended Warehouse Management (SAP EWM)

510

47

SAP Online Help

20.07.2007

You can specify the maximum dimensions that a product is permitted to have to be valid for a certain route. The system compares these dimensions with those that you defined in the product master. You can also define various lead times for the different request types. These influence the start time of a trip in scheduling.

SAP Extended Warehouse Management (SAP EWM)

510

48

SAP Online Help

20.07.2007

Cross-Docking Route Definition One or more inbound routes or one or more outbound routes that are connected by exactly one cross-docking location (warehouse or distribution center relevant to cross-docking).

Use You use cross-docking routes (CD routes) to link routes to route networks. The system takes into account CD routes when you use route determination [Seite 638] as part of cross-docking [Seite 544]. Here you can define per route pair (inbound route and outbound route) whether goods at the cross-docking location (CD location) are to remain on the same vehicle or whether they are be loaded onto a different vehicle.

Structure To define a CD route, you must make the following settings: ●

You specify a CD location for the route at header level.

●

You specify one or more inbound routes on the CD Routes tab page. Here the destination location of all these routes must be identical with the CD location.

●

You specify one or more outbound routes on the CD Routes tab page. Here the start location of all these routes must be identical with the CD location. By specifying a different CD route as the inbound or outbound route, you can create a route network with multiple CD locations. Here an outbound CD route from CD location 1 must have at least one inbound route with the start location CD location 1. An inbound CD route to CD location 2 must have at least one outbound route with the destination location CD location 2.

●

On the CD Attributes tab page, you define the required attributes, for example, whether transshipment is not required (goods remain on the same vehicle), for the route pairs that consist of inbound and outbound routes.

You define CD routes in the master data for Extended Warehouse Management (EWM) under Master Data → Shipping and Receiving → Route Determination → Maintain Route.

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

SAP Extended Warehouse Management (SAP EWM)

510

49

SAP Online Help

20.07.2007

Cross-Docking Route 2 CrossDocking Location 2

Rou (Inb te 1 oun d)

ute Ro

3 ute Ro

2

CrossDocking Location 1

e6 Rout

Rou te 5

Rou (Ou te 4 tbo und )

Cross-Docking Route 1

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

SAP Extended Warehouse Management (SAP EWM)

510

50

SAP Online Help

20.07.2007

Vehicle Definition A specialization of a particular means of transport. A vehicle can comprise one or more transportation units [Seite 613].

Use You define vehicles in the master data for transportation. You use vehicles to group deliveries and to communicate with invoicing and Transportation Management (TM) [Seite 629]. If you assign transportation units to a vehicle in a fixed way, you cannot assign these transportation units to another vehicle. In this case, data that you define for the vehicle is also valid for the assigned transportation units. The dimensions of the vehicle come from the means of transport that you assign to the vehicle, and are used as the planned size.

Integration ●

When the loading process has been completed, a status change triggers the sending of a message to TM that enables bills of lading to be created automatically (see Integration of TM with the Loading Process [Seite 635]).

●

Before goods issue posting, you can create the current invoice via an invoice request to SAP CRM Billing (see Invoice Creation Before Goods Issue [Seite 368]).

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

SAP Extended Warehouse Management (SAP EWM)

510

51

SAP Online Help

20.07.2007

Transportation Unit Definition The smallest loadable unit of a vehicle [Seite 612] that is used to transport goods. The transportation unit (TU) can be a fixed part of the vehicle. The following figure shows different transportation units: ●

Vehicle 1: Semitrailer truck with one transportation unit

●

Vehicle 2: Truck with cargo area and trailer, in other words, two transportation units

●

Vehicle 3: Train with four wagons, in other words, four transportation units Transportation Unit 1

Vehicle 1

Vehicle 2

Transportation Unit 1

Transportation Unit 2

Vehicle 3 TU 1

TU 2

TU 3

TU 4

You map transportation units as handling units (HUs) and assign packaging materials to them. By linking these packaging materials to means of transport, you define construction rules for your vehicles. In this way, you define, for example, how many transportation units a vehicle is supposed to have and the order in which they are to be arranged. You also specify whether a transportation unit is to be optional or obligatory: ●

Obligatory transportation units are a fixed part of a vehicle (fixed assignment). You cannot assign them to another vehicle, for example, truck cargo area.

●

You can assign optional transportation units to other vehicles, for example, trailer for a truck.

Use You define transportation units in the master data for transportation. You use them for inventory management in the yard.

Example The following are additional examples of transportation units: ●

Compartment in a tank truck

●

Container

SAP Extended Warehouse Management (SAP EWM)

510

52

SAP Online Help

20.07.2007

Supply Chain Unit (SCU) Definition Physical or organizational unit that is used with one or more business characters within a logistical process. An organizational unit may be a goods receiving office or a shipping office, for example. The business characters are predefined by SAP.

Use With the SCU, you can replicate certain business characters of locations, such as door or warehouse, which you need in the processes of Extended Warehouse Management (EWM). You can use an SCU with different business characters. An SCU can simultaneously be used as a planning location and a shipping office, for example. You can create hierarchies of SCUs to represent the organization of a supply chain. You can create, change, and delete SCUs via the SAP menu, under Extended Warehouse Management → Master Data → Maintain Supply Chain Unit.

Structure The SCU contains general data and address data of the corresponding location. In contrast to the latter, however, it does not contain any further global or application-specific data. The SCU also has one or more business characters. You will find this SCU data on the following tab pages: ●

General General header data of the SCU/location, such as the global location number (GLN) and geographical data. The technical name of an SCU must be unique in the system. That is to say, it must not conflict with the technical name of a location.

●

Address Data Address data of the location/SCU

●

Business Character One or more business characters of the SCU.

Integration When a location is created in SAP SCM either manually or by transfer via the core interface (CIF), the system automatically creates an SCU with identical general and address data and the business character planning location. Conversely, if you create an SCU with the business character planning location, the system automatically creates a location with identical general and address data.

This relationship is of significance when a location is deleted. When you delete a location, the system only deletes the business character planning location of the corresponding SCU. If the SCU has further business characters, it remains in the system with the same name. To delete the SCU from the system, you must first delete all other existing business characters. If you create an SCU with the business character Warehouse, the system does not create a corresponding location.

SAP Extended Warehouse Management (SAP EWM)

510

53

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

54

SAP Online Help

20.07.2007

Warehouse Task Definition Document that uses Extended Warehouse Management (EWM) to execute goods movements. Logical or physical goods movements or even stock changes can be the basis for a warehouse task. These include: ●

Picks

●

Putaways

●

Internal goods movements

●

Posting changes

●

Goods receipt postings

●

Goods issue postings

Use You create the warehouse task either with reference to a warehouse request or without a reference document, for example for internal goods movements. The following figure shows the different warehouse tasks for products and handling units (HUs): Product Warehouse Tasks [Seite 406] Handling Unit Warehouse Tasks [Seite 407] PROD WT

HU WT

PROD WT HU WT

HU WT

Product Warehouse Task Handling Unit Warehouse Task

You or the system use product warehouse tasks, for example, for deconsolidation [Seite 298] and handling unit warehouse tasks, for example, for unloading [Seite 608]. You can identify the type of the warehouse task from the warehouse process type in the warehouse task. For more information about the simultaneous use of product warehouse tasks and handling unit warehouse tasks, see Pick Point [Seite 410]. EWM also submits hazardous substance texts [Seite 969] in the warehouse task. When you confirm a warehouse task, you can also perform a physical inventory at the same time [Seite 670]. Here, EWM can work with the low-stock physical inventory.

SAP Extended Warehouse Management (SAP EWM)

510

55

SAP Online Help

20.07.2007

Warehouse Order Definition Document that represents an executable work package that a warehouse employee should perform at a specific time. The warehouse order consists of warehouse tasks or physical inventory items.

Use When you move products, in other words you or Extended Warehouse Management (EWM) create warehouse tasks, then EWM groups these warehouse tasks together into warehouse orders, and makes them available for processing. When you perform a physical inventory, in other words you create physical inventory items, EWM also groups these physical inventory items together into warehouse orders. You can adjust the scope and type of a warehouse order using the warehouse order creation rules that you have defined in Customizing.

For more information about warehouse order creation rules, see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Order → Define Creation Rule for Warehouse Orders.

Integration The warehouse groups together warehouse tasks or physical inventory items.

Example EWM creates warehouse tasks for an outbound delivery with four delivery items. EWM uses warehouse order creation to assign the resulting four warehouse tasks to a new warehouse order. A warehouse employee receives this warehouse order as a work package to pick the items listed in the delivery.

SAP Extended Warehouse Management (SAP EWM)

510

56

SAP Online Help

20.07.2007

Handling Unit (HU) Definition A handling unit is a physical unit consisting of packaging materials (load carriers/packing material) and the goods contained on/in it. A handling unit is always a combination of products and packaging materials [Seite 492]. All the information contained in the product items, for example, about batches, is retained in the handling units and is always available. Handling units can be nested, and you can create a new handling unit from several other handling units. A handling unit has a unique, scannable identification number that you can construct according to industry standards such as EAN 128 or SSCC. Pallet = HU 110

Pallet = HU 120

Package HU 111

Package HU 121

©

SAP AG

Package HU 112

Filename

Container = HU 100

Package HU 122

Date/ 1

Fig. 1: Example of a Handling Unit

Structure The object ‘Handling Unit’ contains the following attributes: ●

Identification number

●

Dimension

●

Weight

●

Volume

●

Status

●

Products and quantities

●

Packaging material

●

Packaging specification

A handling unit consists of a handling unit header and handling unit items. It receives a unique number that is used for identification purposes.

Handling Unit Header The header data of a handling unit is divided up as follows: ●

Weight/volume/dimension

●

General data

●

Storage-specific data

SAP Extended Warehouse Management (SAP EWM)

510

57

SAP Online Help

20.07.2007

For more information about the different detailed information, see Packing at the Work Center [Seite 506].

Status The handling unit is connected to general status management. This enables you to document the various physical statuses (such as planned or realized) and other attributes (such as, weighed, loaded, blocked, or posted for GI) for a handling unit. If you want to use your own status, you can store a user schema for the packaging material type.

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

SAP Extended Warehouse Management (SAP EWM)

510

58

SAP Online Help

20.07.2007

Monitoring Purpose The following options are available to you in monitoring: ●

Warehouse Management Monitor [Seite 878]

●

Easy Graphics Framework [Seite 68]

SAP Extended Warehouse Management (SAP EWM)

510

59

SAP Online Help

20.07.2007

Warehouse Management Monitor Use The warehouse management monitor is a central tool for keeping warehouse managers constantly up-to-date as to the current situation in the warehouse, and to enable them to initiate appropriate responses in light of this situation. The warehouse management monitor also contains alert monitoring capabilities, which highlight to warehouse managers actual and potential problematic situations in the warehouse, and provide exception handling tools.

Prerequisites You have accessed the warehouse management monitor by: ...

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

Features

Node Hierarchy Tree

Upper View Area

Lower View Area

Node Hierarchy Tree The node hierarchy tree [Extern] contains all of the predefined nodes representing different object classes. The tree is used solely for navigation purposes. You can use the hierarchy tree to display in the upper view area object information for a specific node, based on selection criteria. The warehouse management monitor contains nodes for object classes relating to the following: ●

Documents such as warehouse requests (WRs) [Extern], warehouse orders (WOs), warehouse tasks (WTs), and physical inventory documents

SAP Extended Warehouse Management (SAP EWM)

510

60

SAP Online Help

20.07.2007

●

Processes such as stock and bin, and resource management [Seite 750]

●

Alerts such as overdue waves [Seite 769] or overdue deliveries without goods issue/goods receipt

Drilldown Capabilities After displaying in the upper view area object information for a node, you can drill down and display the object information for its lower-level nodes, via designated pushbuttons. You can similarly drill down to the lower-level nodes from the lower view area. List and Form Views By default, object information is displayed as a list view [Extern]. The list view is displayed in an ALV grid, and offers all standard ALV functionalities, including sorting, filtering and printing. You also have the option of toggling to form view [Extern] for a selected object. The form view provides a focused view of the object, and provides more detailed information than the list view. The form view is displayed in an HTML viewer. Methods After object information is displayed in either view area, you can call methods to perform actions on selected objects. For more information about the available methods, see Monitor Methods [Seite 882]. Customizing Options You can use the standard SAP monitor or you can create your own monitor in Customizing.

For more information about creating your own monitor, see the Implementation Guide (IMG) for EWM under Extended Warehouse Management → Monitoring → Warehouse Management Monitor. If you use the standard SAP monitor, you can tailor it to your needs by either creating variants for the standard nodes, or creating new variant nodes, based on the standard nodes. ●

Creating variants for the standard nodes enables you to use predefined selection criteria while running a session of the monitor. The variant-node assignments are lost when you close the monitor session.

●

Creating variant nodes enables you to create your own nodes, which are based on the standard nodes, but with specific selection criteria, or with a specific layout. Variant nodes are always available when the user utilizes the monitor.

SAP Extended Warehouse Management (SAP EWM)

510

61

SAP Online Help

20.07.2007

Monitor Basic Operations Use Functions Function

What You Should Know

Hide a selected node in the hierarchy tree

This operation is invoked by choosing the Hide Node option in the node’s context menu.

Show hidden nodes

This operation is invoked by choosing Show Hidden Nodes. After choosing this option, previously hidden nodes are displayed in the icon. hierarchy tree, with the

Unhide a selected node in the hierarchy tree

This operation is invoked by choosing the Unhide Node option in the node’s context menu. After choosing this option, the node icon changes to (regular node) or (variant node).

Create a variant node in the hierarchy tree

There are two options from the node’s context menu: Create Variant Node for Current Level – creates a variant node directly underneath the original node Create Variant Node for Category Level – creates a variant node under the original node, on the same level as the node’s category When creating the variant node, you have one of the following execution options: Execute – creates only the variant node based on the source node Execute with Sub-Tree – creates the variant node, as well as all of the same lower-level nodes as are contained in the source node After creating the variant node, you can create a variant for selection criteria, as well as assign to it a layout variant.

Delete variant node

This operation is invoked by choosing the Remove Node option in the node’s context menu.

Change variant node text

This operation is invoked by choosing the Rename Node option in the node’s context menu.

Display in list view object information for a node

This operation is invoked either by double-clicking the node, or choosing the Set Selection Criteria option in the node’s context menu.

SAP Extended Warehouse Management (SAP EWM)

510

62

SAP Online Help

20.07.2007

Expand all nodes in the hierarchy tree

This operation is invoked by choosing in the top tool bar.

Collapse all nodes in the hierarchy tree

This operation is invoked by choosing in the top tool bar.

Display object information of a lower-level node in the higherlevel node’s list view

This operation is invoked by selecting a row in the ALV, and choosing the pushbutton corresponding to the lower-level node. Information on the lower-level objects appears in the bottom list view.

Toggle between list and form views

You call this operation by selecting one or more rows in the ALV, and choosing from the list view tool bar. You can toggle back from form view again. to list view, by choosing

Show display transaction for object

SAP Extended Warehouse Management (SAP EWM)

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

510

63

SAP Online Help

20.07.2007

Monitor Methods Use The warehouse management monitor methods enable you to manage and control warehouse objects and processes. The methods are assigned to object classes, and carried out on specific objects within the object classes. They are implemented by utilizing function modules from content providers responsible for the object classes.

Prerequisites You have defined object class methods, and their presentation, in Customizing for Extended Warehouse Management → Monitoring → Warehouse Management Monitor → Define Object Class Methods.

Methods are included in the standard delivery. The methods are displayed as standard with the accumulated methods menu buttons.

Activities Standard Monitor Methods Method Name

Object Class Name

Display Bin

Displays data for the selected storage bin (transaction /SCWM/LS03) BIN

Storage Bin

Change Bin Print

Description

Presentation Text

Enables you to change data of the selected storage bin (transaction /SCWM/LS02) HU

Handling Unit

WO

Warehouse Order

HU

Handling Unit

WT

Warehouse Task

WO

Warehouse Order

Display HU

HU

Handling Unit

Enables you to display detailed information for an HU at a work center

Display PI Doc.

PIDIFF

Differences-{}-

Enables you to display or process a physical inventory document (transaction /SCWM/PI_PROCESS)

Process PI Doc.

PIDLOC

Storage Bin

PIDSTK

Product

PIHHU

Handling Unit

PIHIST

Doc. History

PIHLOC

Storage Bin

PIHREF

References

Reprint

Enables you to print HU or WO details

Enables you to reprint HU, WT or WO details

SAP Extended Warehouse Management (SAP EWM)

510

64

SAP Online Help

20.07.2007

PIHSTK

Product

PISLOC

Storage Bin

Maint. Resource

Enables you to maintain a selected resource [Seite 752] (transaction /SCWM/RSRC)

Logon Resource

Enables you to log on a selected resource to the desktop environment

RSRC

Resource

Logoff Resource

Enables you to log off a selected resource from the desktop environment

Send Message

Enables you to create and send a message to one or more selected resources

Assign Queue Unassign Queue

RSRCG R

Resource Group

Simulate WO

Enables you to assign/unassign a queue [Seite 764] to/from the selected resource group [Seite 754] (transaction /SCWM/QSEQ)

Enables you to simulate WO creation for one or more selected WTs, based on a specified WO creation rule. If none is specified, the system will attempt to determine one pursuant to the search sequence for WO creation rules per activity area.

Display WT Log

Displays the application log for a selected WT

Split from WO

Enables you to unassign one or more WTs from a WO, and group them into a newly-created WO.

WT

Warehouse Task

Using this method, you can determine the warehouse creation rule. If none is specified, the system will attempt to determine one pursuant to the search sequence for WO creation rules per activity area. You can also specify a reason for the split, which is stored in the exception log for WOs.

Assign WT

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

Unassign WT

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

To execute the WTs, you will need to assign them to a WO. Cancel WT

Enables you to cancel a WT

Confirm Foregr.

Enables you to confirm in the foreground one or more selected WTs or WOs (transaction /SCWM/TO_CONF)

Confirm Backgr. Create User

WT

Warehouse Task

WO

Warehouse Order

USER

User(s)

Confirms in the background one or more selected WTs or WOs Enables you to create/maintain a user (transaction /SCWM/USER)

Maintain User

SAP Extended Warehouse Management (SAP EWM)

510

65

SAP Online Help

20.07.2007

Hold Wave

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

Unhold Wave

Sets the status of the selected waves to Initial

You can perform this method only on waves of status On Hold. Delete Wave

Deletes the selected waves. WAVE

Wave

All the wave items are unassigned from the waves

Merge Wave

Merges the selected waves into one wave.

Change Wave

Enables you to change the attributes of a selected wave

Release Wave

Releases one or more selected waves

The merged wave inherits its attributes from the first wave

You can release only those waves of status Initial. Subsyste m

Activates the WOs and WTs sent to a subsystem

Split WAVITM

Wave Item

Unassign

Unassigns the selected wave items from the wave

Assign to Wave

WAVITM

Wave Item

WHRITO

Warehouse Request Item

Display WR

WHRI

Warehouse Request (Inbound)

WHRO

Displ. Insp.Doc

Enables you to assign one or more selected wave items or WR items to a specified wave

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

Warehouse Request (Outbound)

WHRI

Warehouse Request (Inbound)

WHRO

Warehouse Request (Outbound)

WHRITI

Display WO Log

Splits the selected wave items from their waves, and creates a new wave for them

Displays the inspection document(s) and inspection outcomes for a selected WR or WR item

Warehouse Request Item (Inbound)

WHRITO

Warehouse Request Item (Outbound)

WO

Warehouse Order

Displays the application log for a selected WO

SAP Extended Warehouse Management (SAP EWM)

510

66

SAP Online Help

Merge WOs

20.07.2007

Enables you to merge selected open WOs, which unassigns the WTs from the WOs, and groups them into a newly-created WO. Using this method, you can determine the warehouse creation rule. If none is specified, the system will attempt to determine one pursuant to the search sequence for WO creation rules per activity area. You can also specify a reason for the merge, which is stored in the exception log for WOs.

Hold WO

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

Open WO

Sets the status of one or more selected WOs to Open.

Add WO

Adds an empty WO to a super WO (loading/unloading scenario)

Assign Rsrce

Enables you to assign/unassign a resource to/from one or more selected WOs

Unassign Rsrce Queue ändern

Enables you to change the queue to which the selected WOs are assigned

Change LSD

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

SAP Extended Warehouse Management (SAP EWM)

510

67

SAP Online Help

20.07.2007

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

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

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

Integration ●

By default, the EGF uses SAP Internet Graphics Server (SAP IGS) as its graphics provider to generate graphics from data. You can however use any other graphics provider that generates graphics from data. These graphics must be transferred to the EGF in the form of Uniform Resource Locators (URLs) (see Make Settings for the Easy Graphics Framework [Seite 73]).

●

The service provider defines which data the EGF displays for an EGF object.

●

To ensure that the EGF can be displayed without errors, you must have installed Microsoft Internet Explorer version 5 or higher. For more information about security settings in Internet Explorer, see SAP Help Portal under help.sap.com → mySAP ERP → SAP ERP Central Component → Logistics → Production Planning and Control (PP) → Production Planning for Process Industries (PP-PI) → Process Management (PP-PI-PMA) → Process Instruction Sheets (PI Sheets) → Browser-Based PI Sheet → Setting Up the Browser for PI Sheets and Cockpits.

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

SAP Extended Warehouse Management (SAP EWM)

510

68

SAP Online Help

20.07.2007

Display

Call corresponding to Customizing

Easy Customizing Graphics Framework

URL for generated graphic

Graphics Provider • SAP Internet Graphics Server • Customer-Specific

Drilldown

The EGF receives data from a service provider, for example about the utilization of resources. If you are using a chart type to display this data that is delivered in the standard SAP system, the EGF sends the data to SAP IGS. If you are using your own chart type to display this data, the EGF uses method GET_URL to send the data to your graphics provider (see Interfaces [Seite 77]). SAP IGS or your graphics provider generates a relevant graphic, and sends a URL to the EGF. The EGF uses this URL to display the graphic in your cockpit. The following functions are available in the EGF: ●

By default, the EGF uses SAP IGS as a graphics provider. You can use a selection of chart types [Extern], which are provided by SAP IGS. The EGF also provides you with further chart types, such as traffic lights. You can also use your own graphics provider and your own chart types (see Make Settings for the Easy Graphics Framework [Seite 73]).

●

The EGF displays all chart types that you have defined in Customizing for the EGF. The EGF also shows all chart types for which a graphics provider sends a URL that refers to this chart type. This can be SAP’s own graphics, such as from SAP xApp Manufacturing Integration and Intelligence (xMII) or Business Server Page applications, or graphics from external providers (see Make Settings for the Easy Graphics Framework [Seite 73]).

●

You can display graphics either in a cockpit, with or without Customizing, or in your own application (see Make Settings for the Easy Graphics Framework [Seite 73] und Interfaces [Seite 77]).

●

The EGF displays the current data sent by a service provider, and refreshes this data in specified intervals. You can define the input data for a displayed EGF object, including the refresh rate (see Using the Refresh Rate [Seite 76]).

●

If you have defined follow-up activities, you can navigate from the graphic in the EGF to another application (see Make Settings for the Easy Graphics Framework [Seite 73]). For example, you display the number of open warehouse tasks in a graphic, and have defined a follow-up activity to navigate to warehouse task confirmation. If you want to navigate from the EGF to a follow-up activity, you can do this in one of the following ways: ○

In the context menu of the EGF object, select the corresponding option.

SAP Extended Warehouse Management (SAP EWM)

510

69

SAP Online Help ○ ●

20.07.2007

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

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

You have the EGF objects Door Assignment and Unconfirmed Warehouse Tasks in a cockpit. You want user A to be able to see only the EGF object for unconfirmed warehouse tasks in the navigation tree of the cockpit, and define authorizations correspondingly. You want user B to see only unconfirmed warehouse task data for warehouse numbers 0001 and 0002, and define authorizations correspondingly. For more information, see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Authorization Groups. ●

You can define a cross-user or a user-specific EGF cockpit layout. For an EGF cockpit menu, for example, you can define a changed structure in the navigation tree with newly created structure nodes (see Definition of EGF Cockpit Layouts [Seite 71]).

●

In Customizing for the EGF, you can define the following for displaying EGF objects (see Make Settings for the Easy Graphics Framework [Seite 73]): ○

Cockpit

○

Available EGF objects for each cockpit

○

Available chart types for each EGF object

○

Default chart type You can specify a default chart type for each EGF object.

○

Input data for an EGF object

○

Follow-up activities for each EGF object

SAP Extended Warehouse Management (SAP EWM)

510

70

SAP Online Help

20.07.2007

Definition of EGF Cockpit Layouts Use You can define different EGF cockpit layouts either user-specifically or cross-user.

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

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

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

Default layout of an EGF cockpit

If you do not define a default layout, the EGF displays both the standard SAP EGF objects and your own EGF objects. You can reload a cockpit layout at any time, for example if you have deleted EGF objects from the navigation tree and want to display them again. ●

Grouping of EGF objects in the navigation tree, to display your EGF objects in a clearer way

●

Saving input data, such as the warehouse number

●

Number of rows and columns of the display grid and the layout of the grid You can divide a cell of a grid into further rows and columns. You can also insert a grid within a grid, or define the size of the individual viewers.

●

Size of the displayed graphic If you change the display size of a displayed EGF object, the EGF automatically adjusts the size of the displayed graphic as soon as the next refresh interval [Seite 76] has occurred. If you choose with the quick info Regenerate Graphics, the EGF adjusts the display size for EGF objects that are already displayed straight away.

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

Layout name

●

Description

●

Layout options: ○

EGF cockpit menu only

○

EGF cockpit menu and grid layout

○

EGF cockpit menu, grid layout, and input data

SAP Extended Warehouse Management (SAP EWM)

510

71

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

72

SAP Online Help

20.07.2007

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

Settings for EGF Objects ●

If you want to display a graphic in a cockpit, define your own chart types and assign these or existing chart types to EGF objects. To do this, in Customizing for EWM, execute the IMG activity Define Chart Types and Define Objects. For more information, see the Implementation Guide (IMG) for EWM under Monitoring → Easy Graphics Framework → Define Chart Types and Define Objects.

●

If you navigate from a displayed EGF object to follow-up activities, and want to use the Post Processing Framework or a workflow, define follow-up activities. To do this, in Customizing for EWM, execute the IMG activity Define Functions. For more information, see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Functions.

●

If you want to define authorizations for each EGF object or function, define authorization groups and assign these to an EGF object or function. To do this, in Customizing for EWM, execute the IMG activity Define Authorization Groups and Define Objects. For more information, see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Objects.

The EGF only performs the authorization check for EGF objects. If you define a navigation to follow-up activities and follow-up objects, you have to perform an authorization check yourself. ●

You define the default chart type for an EGF object. To do this, in Customizing for EWM, you specify the default chart type for an EGF object in the Chart Type field of IMG activity Define Objects. For more information, see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Objects.

●

If you want to change the predefined refresh rate, define your own refresh rate. To do this, in Customizing for EWM, you specify your refresh rate in the Interval column of dialog structure Objects in the IMG activity Define Objects (see Using the Refresh Rate [Seite 76]). For more information, see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Objects.

Settings for Displaying EGF Objects in the Navigation Tree of the EGF Cockpit ●

You specify the cockpit for displaying an EGF object by defining a new EGF implementation. To do this, in Customizing for EWM, execute the IMG activity Define Cockpits. For more information, see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Cockpits.

●

You define the number of EGF objects for each cockpit. To do this, in Customizing for EWM, specify the number in dialog structure Cockpits → Objects in IMG activity Define Cockpits. For more information, see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Cockpits.

●

You define input data for an EGF cockpit. To do this, in Customizing for EWM, specify the number in dialog structure Cockpits → Input Data in IMG activity Define Cockpits. For more information, see the IMG for EWM under Monitoring → Easy Graphics Framework → Define Cockpits.

SAP Extended Warehouse Management (SAP EWM)

510

73

SAP Online Help

20.07.2007

Settings for Graphics ●

You define the attributes of a graphic for each EGF object, such as per resource or warehouse task, or per user. For example, you can define that the background color in graphics is always blue, or that EGF is to always use blue, yellow, red and green to display pie charts. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Monitoring → Process Chart Template. Make your changes, and save them. When saving, you can choose between User-Specific and Cross-User. You have defined the authorizations per EGF object or user if required. You can assign the following authorizations: ○

You can define a chart type, and allow it as a default chart type for all users, EGF cockpits, and EGF objects.

○

You can define a chart type, and allow it as a default chart type for user USER1, all EGF cockpits, and all EGF objects.

○

You can define a third chart type, and allow it as a default chart type for user USER2, EGF cockpit COCKPIT2, and EGF object OBJECT2.

User

EGF Cockpit

EGF Object

Chart Type

Default Chart Type

*

*

*

PIE CHART

DEFAULT

USER1

*

*

PIE CHART

DEFAULT1

USER2

COCKPIT2

OBJECT2

PIE CHART

DEFAULT2

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

Settings for Your Own Graphics ●

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

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

SAP Extended Warehouse Management (SAP EWM)

510

74

SAP Online Help ■ ■

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

service.sap.com/securityguide → SAP Supply Chain Management → SAP Supply Chain Management Security Guide SCM 5.1

●

■

SAP Help Portal at help.sap.com → SAP R/3 Enterprise Release 4.70 → SAP NetWeaver Components → SAP Internet Transaction Server → ITS Implementation Models → WebRFC Programming ### Web Reporting.

■

SAP Help Portal under help.sap.com → SAP NetWeaver 2004s → SAP NetWeaver Library → SAP NetWeaver by Key Capability → Application Platform by Key Capability → ABAP Technology → UI Technology → Front-End Services (BC-FES) → SAP HTML Viewer (BCCI)

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

SAP Extended Warehouse Management (SAP EWM)

510

75

SAP Online Help

20.07.2007

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

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

76

SAP Online Help

20.07.2007

Interfaces, Methods and Function Modules in the EGF Use The Easy Graphics Framework (EGF) allows you to work with various interfaces, methods, and function modules.

Features Interfaces and Methods The following table gives you an overview of the methods in the EGF. Interface

Method

Description

/SCWM/IF_EGF_SP

GET_DATA

Gets chart data from the application. Most charts require a group of row values and a group of data categories as data format. A simple chart, such as a traffic light, only sets the color of the traffic light.

/SCWM/IF_EGF_SP

GET_URL

Gets a URL from the application. This URL forms the link to the graphic that the EGF is to display.

/SCWM/IF_EGF_SP

HANDLE_FUNCTION

If the application receives a function code for a follow-up activity, this interface method enters the function code for the chart.

SCWM/IF_EGF_CHART

CREATE_CHART

Generates graphic of a graphics provider in the EGF, such as for all EGF graphics of class /SCWM/CL_EGF_IGS_SERVICES in interface /SCWM/IF_EGF_CHART.

You can use these interfaces to do the following: ●

Define a source for your chart data

●

Define your own graphics provider

●

Define your own chart types and send them to the EGF using a URL

●

Define follow-up activities for an EGF object

For more information, see the interface documentation.

Function Modules The following table gives you an overview of the function modules in the EGF. Function Module

Description

/SCWM/EGF_COCKPIT

Starts an EGF cockpit implementation. You must enter the cockpit ID as an import parameter.

SAP Extended Warehouse Management (SAP EWM)

510

77

SAP Online Help

20.07.2007

/SCWM/EGF_CONTAINER

You transfer a container instance to the function module, such as to class CL_GUI_CUSTOM_CONTAINER, in which the required EGF object is displayed.

/SCWM/EGF_POPUP

The system generates a modeless dialog box in which the required EGF object is displayed.

/SCWM/EGF_COCKPIT_DYNAMIC

Starts an EGF cockpit dynamically. All the data required for generating the cockpit is transferred using the interfaces of the function module. No Customizing is required here.

/SCWM/EGF_CONTAINER_DYNAMIC

You transfer a container instance to the function module, such as to class CL_GUI_CUSTOM_CONTAINER, in which the required EGF object is displayed. The EGF object definition is done dynamically using the interface of the function module. No Customizing is required here.

/SCWM/EGF_POPUP_DYNAMIC

The system generates a modeless dialog box in which the required EGF object is displayed. The EGF object definition is done dynamically using the interface of the function module. No Customizing is required here.

You can use these function modules to do the following: ●

Start an EGF cockpit implementation

●

Transfer a container instance to a function module

●

Generate a modeless dialog box You can display a graphic as a subscreen or as a separate modeless dialog box in your application. To do this, choose the following in Customizing for EWM: Monitoring → Easy Graphics Framework → Define Chart Types and Define Cockpits.

For more information, see the function module documentation.

SAP Extended Warehouse Management (SAP EWM)

510

78

SAP Online Help

20.07.2007

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

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

Procedures ...

1. In the Internet Explorer menu, choose Tools → Internet Options. 2. Choose the Security tab page. 3. Choose the Web content zone: Under Internet Options, you can choose from different options. We cannot recommend Internet. Trusted Sites is safer, but Local Intranet offers better performance (see also SAP Note 785308). 4. Choose Custom Level.... 5. In the Security Settings window, make the following settings: Function

Setting

Download signed ActiveX controls

Prompt

Launching programs and files in an IFRAME

Prompt

Navigate sub-frames across different domains

Prompt

SAP Extended Warehouse Management (SAP EWM)

510

79

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

80

SAP Online Help

20.07.2007

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

Inbound delivery process The following inbound delivery scenarios are supported by delivery processing: ●

Deliveries to the customer, to the warehouse, to any ship-to party, or to any ship-to location.

●

Returns to the supplier, to any ship-to party or to any ship-to location.

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

Outbound delivery process The following outbound delivery scenarios are supported by delivery processing: ●

Deliveries from the supplier, from any ship-from party or from any ship-from location.

●

Returns from the customer, from any ship-from party or from any ship-from location.

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

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

Status management [Seite 94]

●

Quantity offsetting [Seite 97]

●

Text management

For more information about text management in delivery processing, see the documentation for the relevant SAP application (for example, mySAP Supply Chain Management → SAP Extended Warehouse Management). ●

Field control [Seite 99]

SAP Extended Warehouse Management (SAP EWM)

510

81

SAP Online Help ●

Validation [Seite 101]

●

Connection to the Post Processing Framework (PPF) [Seite 105]

●

Change documents [Seite 107]

●

Archiving

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

82

SAP Online Help

20.07.2007

Documents in Delivery Processing Use A document contains all the data required to document and control a business process. Various documents are used in delivery processing to control the processes. The inbound delivery process is represented in the system by the following documents: ●

Inbound Delivery Notification [Seite 87]

●

Inbound Delivery [Seite 88]

The outbound delivery process is represented in the system by the following documents: ●

Outbound Delivery Request [Seite 90]

●

Outbound Delivery Order [Seite 91]

●

Outbound Delivery [Seite 93]

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

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

Header

Item 1

e.g. Shipping point, goods recipient

e.g. Material, quantity

Item 2

Item 3

Document header The document header contains the general data for the inbound or outbound delivery. This data is relevant for the complete document. It includes: ●

Goods receiving point or shipping point

●

Scheduling data (for example, shipping or delivery date)

●

Weights and volumes for the complete inbound/outbound delivery

●

Supplier, sold-to party and goods recipient numbers

SAP Extended Warehouse Management (SAP EWM)

510

83

SAP Online Help

20.07.2007

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

Document cat. IDR

Document cat. PDI

Inbound delivery

Inbound delivery

notification

Document type Z100

Inbound delivery process

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

Document cat. IDR

Document cat. PDI

Inbound delivery notification

Inbound delivery

Document type Z100

Document type Z200 Document type Z300

Inbound delivery process

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

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

SAP Extended Warehouse Management (SAP EWM)

510

84

SAP Online Help

20.07.2007

●

Material number

●

Delivery quantity

●

Location specifications (goods receiving point, unloading point or shipping point)

●

Putaway date or picking date

●

Weights and volumes of the individual items

●

Tolerances for underdelivery or overdelivery

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

Normal delivery item

●

Return item

●

Text item

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

Service profiles Service profiles define how a document is processed in the system as well as its business scope. Two types of service profile exist: ●

System profile

●

Customer profile (for example, status profile, text profile and incompleteness profile)

The system profile is not configurable and is linked to the document categories and item categories. The customer profiles are linked to the document types and to the item types. In Customizing for Delivery Processing, you can define more customer profiles and therefore adjust the documents to suit your business process. In delivery processing, you can configure the following functions using the customer profiles: ●

Status management

●

Quantity offsetting

●

Text management

●

Field control

●

Incompleteness check

●

Actions

●

Partner processing

●

Process codes

●

Reference document types

SAP Extended Warehouse Management (SAP EWM)

510

85

SAP Online Help ●

20.07.2007

Date types

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

General Settings The general settings for the documents in delivery process are not controlled by the service profiles. You can define the following general settings in Customizing for Delivery Processing: ●

Number range intervals

●

Delivery priority

●

Shipping conditions

●

Incoterms

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

SAP Extended Warehouse Management (SAP EWM)

510

86

SAP Online Help

20.07.2007

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

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

Structure The inbound delivery notification comprises the following: ●

Document category with the same name Inbound Delivery Notification

●

Document type

●

Item category

●

Item type

●

Service Profiles

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

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

The delivery process receives a message from a reference document with all the relevant logistics data. An inbound delivery notification is created automatically as a result of this message. All the information contained in the message is saved in the inbound delivery notification. An inbound delivery is created automatically from the inbound delivery notification.

●

Changing an existing inbound delivery: If a change to an existing inbound delivery is rejected, an inactive inbound delivery notification (inactive version) is created in addition to the existing active inbound delivery notification. You can process the data in the inactive inbound delivery notification and you can create a new inbound delivery by activating the request manually.

SAP Extended Warehouse Management (SAP EWM)

510

87

SAP Online Help

20.07.2007

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

Use The inbound delivery is used as a working object in the inbound delivery process. You use this document in delivery processing when executing the following actions: ●

Registering the delivery in the yard

●

Unloading the delivery

●

Canceling the “unloading of the delivery”

●

Placing the delivery into stock (putaway)

●

Canceling the “delivery putaway”

●

Adjusting the delivery quantity to the quantity posted in the goods receipt (in case of overdelivery or underdelivery.

●

Adjusting the delivery quantity and the transferred quantity In this case, the delivery quantity is adjusted to the quantity posted in the goods receipt. The quantity in the inbound delivery notification is also adjusted and a new inbound delivery is created.

●

Posting a goods movement

●

Canceling a goods movement

●

Creating items

●

Deleting items

You can save, validate and delete an inbound delivery.

Structure The inbound delivery request comprises the following: ●

Document category with the same name Inbound Delivery

●

Document type

●

Item category

●

Item type

●

Service Profiles

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

SAP Extended Warehouse Management (SAP EWM)

510

88

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

89

SAP Online Help

20.07.2007

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

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

Structure The outbound delivery request comprises the following: ●

Document category with the same name Outbound Delivery Request

●

Document type

●

Item category

●

Item type

●

Service Profiles

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

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

The delivery process receives a message from a reference document with all the relevant logistics data. An outbound delivery request is created automatically as a result of this message. The delivery process saves the information from the message in the outbound delivery request. The message itself is not saved. An outbound delivery order is created automatically from the outbound delivery request.

●

Changing an existing outbound delivery order: If a change to an existing outbound delivery order is rejected, an inactive outbound delivery request (inactive version) is created in addition to the existing active outbound delivery request. You can process the data in the inactive outbound delivery request and you can create a new outbound delivery order by activating the request manually.

SAP Extended Warehouse Management (SAP EWM)

510

90

SAP Online Help

20.07.2007

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

Use You either use the outbound delivery order to preview the planning of pending warehouse activities or to execute the actions required to create the delivery. You can use the outbound delivery order to execute the following actions: ●

Creating the delivery and therefore creating an outbound delivery [Seite 93]

●

Picking the delivery

●

Canceling the “delivery picking”

●

Loading the delivery

●

Canceling the “delivery loading”

●

Setting the status Leave Yard

●

Adjusting the delivery quantity to the picked quantity

●

Posting a goods movement

●

Canceling a goods movement

●

Creating items

●

Deleting items

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

Structure The outbound delivery order comprises the following: ●

Document category with the same name Outbound Delivery Order

●

Document type

●

Item category

●

Item type

●

Service profiles

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

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

SAP Extended Warehouse Management (SAP EWM)

510

91

SAP Online Help ●

20.07.2007

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

●

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

SAP Extended Warehouse Management (SAP EWM)

510

92

SAP Online Help

20.07.2007

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

Use The outbound delivery is used as the basis for printing the delivery note or for sending a shipping notification. You can execute the following actions using this document: ●

Posting a goods movement

●

Canceling a goods movement

●

Setting the status Leave Yard

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

Structure The outbound delivery comprises the following: ●

Document category with the same name Outbound Delivery

●

Document type

●

Item category

●

Item type

●

Service profiles

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

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

SAP Extended Warehouse Management (SAP EWM)

510

93

SAP Online Help

20.07.2007

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

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

Features A status in delivery processing consists of the following parameters: ●

Status type

●

Status value

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

At least one status value must allow the transaction.

●

No status value may disallow the transaction.

SAP delivers predefined status types for the standard processes in delivery processing. Several of these status types are indicated by special attributes which are displayed in the following table. You cannot change these attributes in Customizing. Attribute

Meaning

Use

Aggregated status

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.

An aggregated status at document header level provides compact information on the status of all the items, for example in a display or change transaction.

Projected status

The system calculates the status value of such a status type from the status type with the same name from higher document levels.

A projected status at document item level provides the option of controlling activities and the field control at item level by a status at header level. This attribute has a purely technical meaning.

Overall status

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

An overall status provides compact information on a certain quantity of statuses for the same partial object (for example, header or item).

SAP Extended Warehouse Management (SAP EWM)

510

94

SAP Online Help

20.07.2007

example, header or item). Transient status

The system only calculates this status type for the runtime. The status type is not saved permanently.

Status value if original status ambiguous

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.

Inactive

You use this indicator to activate or deactivate several status types in each status profile. However, there are also status types which always have to be active. You cannot change this indicator for these status types.

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

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

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

U1 U1

U2 U2

U3 U3

Ux Ux User Status Sx Sx Predefined Status Type

1:n Object Type 1

Objekt Type 2

1:1 System Profile 1

System Profile 2

S1 S1

S2 S2

S3 S3

S1 S1

S2 S2

S3 S3

U1 U1

U2 U2

U3 U3

U1 U1

U2 U2

U3 U3

1:n Status Profile 1 of Delivery Processing

S1 S1 U1 U1

S3 S3 U2 U2

Status Profile 2 of Delivery Processing

S1 S1

S2 S2 U2 U2

U3 U3

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

SAP Extended Warehouse Management (SAP EWM)

510

95

SAP Online Help

20.07.2007

Actions In Customizing for Delivery Processing [Seite 108], you can execute the following activities: ●

Activate or deactivate certain status types in the status profile

●

Create status profiles

●

Define a user status profile of the general status management for the user status

●

Define user statuses

SAP Extended Warehouse Management (SAP EWM)

510

96

SAP Online Help

20.07.2007

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

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

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

Quantity type

●

Quantity calculation

●

Quantity offsetting

●

Quantity role

●

Quantity offsetting profile

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

Requested quantity

●

Reduced quantity

●

Open quantity

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

97

SAP Online Help

20.07.2007

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

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

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

Activities In Customizing for Delivery Processing, you can execute the following activities: ●

Define quantity type

●

Define quantity type

●

Define quantity offsetting profile

●

Define quantity calculation rules

●

Define quantity offsetting rules

SAP Extended Warehouse Management (SAP EWM)

510

98

SAP Online Help

20.07.2007

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

Integration Field control depends on status management [Seite 94]. During the delivery process, the system controls which fields can be displayed and changed via the status of the document and item type. The field control is accessed by delivery processing during the following events: ●

When creating a document or a document item

●

When switching between display mode and change mode

●

After changing the data in a document

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

Field attributes In the field attributes of the field control, the system defines the status for which a field is displayed and can be changed for each logical field name. Field attributes in the field control Field attribute

Description

Status type

Describes a partial view or a partial process in the processing of a delivery document (for example, goods receipt status, unloading status or putaway status).

Status value

Defines the delivery document status with regard to the status type (for example, Yes/No or Not Started/In Process/Completed).

Display field

If this indicator is set, the field is displayed as a non-changeable field depending on the assigned status (status type and status value).

Hide

If this indicator is set, the field is not displayed depending on the assigned status (status type and status value).

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

SAP Extended Warehouse Management (SAP EWM)

510

99

SAP Online Help

20.07.2007

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

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

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

Activities In Customizing for Delivery Processing [Seite 108], you can execute the following activities for the field control: ●

Define a new field control profile

●

Maintain field attributes You cannot change any of the field attributes delivered by SAP. However, you can add new field attributes.

●

Define logical field names for new fields

●

Add new logical field names to the system profile of the field control

SAP Extended Warehouse Management (SAP EWM)

510

100

SAP Online Help

20.07.2007

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

Features The validation comprises the following checks: ●

Incompleteness Check [Seite 102]

●

Consistency Check [Seite 103] with Tolerance Check [Seite 104]

SAP Extended Warehouse Management (SAP EWM)

510

101

SAP Online Help

20.07.2007

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

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

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

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

Activities The incompleteness check is executed automatically by the system. If the incompleteness check determines a mandatory field that has not been filled, the action is terminated and an appropriate message is issued. In Customizing for Delivery Processing [Seite 108], you can execute the following activities for the field control: ●

Define a new incompleteness profile

●

Maintain field attributes You cannot change any of the field attributes delivered by SAP. However, you can add new field attributes.

●

Define logical field names for new mandatory fields

●

Add new logical field names to the system profile of the field control

SAP Extended Warehouse Management (SAP EWM)

510

102

SAP Online Help

20.07.2007

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

Features The consistency check contains the following checks: ●

Check whether the document type, document category, item type and item category correspond to the settings in Customizing for delivery processing.

●

Check whether the document contains items.

●

Check whether the product data corresponds to the product master (for example, product ID and allowed units of measure).

●

Check whether the location data corresponds to the location master.

●

Check whether the delivery date lies in the past.

●

Check whether the specifications for the Incoterms, process codes, partner roles, reference documents and date types correspond to the settings in Customizing for delivery processing.

●

Check whether partial deliveries are allowed. Delivery processing determines the number of allowed partial deliveries from the reference document. The consistency check uses these specifications to determine whether partial deliveries are allowed. If no partial deliveries are allowed, the system issues a message and you cannot split the delivery.

●

Check whether the retention period is expired.

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

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

SAP Extended Warehouse Management (SAP EWM)

510

103

SAP Online Help

20.07.2007

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

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

Features The tolerance check is split into the underdelivery tolerance and the overdelivery tolerance. ●

Underdelivery tolerance The minimum allowed delivery quantity. It is specified as a percentage.

●

Overdelivery tolerance The maximum allowed delivery quantity. It is specified as a percentage.

As soon as the delivery quantity changes in a document, the delivery process checks to see whether the changed delivery quantity still lies within the defined tolerances. If the goods quantity lies below or above the tolerance values, the system issues a warning message. The tolerance check in delivery processing checks the delivery quantities in the following documents: ●

Inbound Delivery Notification [Seite 87]

●

Inbound Delivery [Seite 88]

●

Outbound Delivery Request [Seite 90]

●

Outbound Delivery Order [Seite 91]

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

Activities The tolerance check is executed automatically by the system.

SAP Extended Warehouse Management (SAP EWM)

510

104

SAP Online Help

20.07.2007

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

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

Features The PPF provides the following functions: ●

Technique for determining actions

●

Technique for aggregating found actions

●

Medium for processing actions

●

User interface for Customizing action templates including determination and aggregation techniques as well as processing mediums

●

User interface for Customizing conditions if you use determination via conditions

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

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

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

Activities In Customizing for Delivery Processing [Seite 108], you can execute the following activities: ●

Define actions

●

Define action profiles

●

Define conditions

Example Examples of actions include: ●

Activate inbound delivery notification

●

Post goods receipt

●

Print delivery note

SAP Extended Warehouse Management (SAP EWM)

510

105

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

106

SAP Online Help

20.07.2007

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

Features As soon as a delivery document is changed and saved by a user, a change document is created in delivery processing. The change document contains the following information: ●

which changes were made to a delivery document

●

which user made the changes

●

when the changes were made

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

SAP Extended Warehouse Management (SAP EWM)

510

107

SAP Online Help

20.07.2007

Menu Paths and Customizing Paths for Delivery Processing This section provides you with information on which SAP application contains the delivery processing component and its functions and where to find this information.

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

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

SAP Extended Warehouse Management (SAP EWM)

510

108

SAP Online Help

20.07.2007

Warehouse Request Definition A warehouse request is a document that enables the processing of warehouse activities for a specific product. The warehouse activities for a product include the following: ●

Picking

●

Putaway

●

Posting change

●

Stock transfer (within warehouse)

●

Scrapping

Use You use this document in Extended Warehouse Management (EWM) to: ●

Process specific product quantities within a warehouse for your goods receipt process or goods issue process (for example, for putaway or picking).

●

Create posting changes [Seite 128]

●

Process internal goods movements [Seite 122]

●

Process scrappings [Seite 130]

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

Structure A warehouse request consists of ●

Document categories with different document types. You can define the document types in Customizing for delivery processing.

For more information about defining document types in EWM, see the Implementation Guide (IMG) for EWM: ●

●

→ Goods Receipt Process → Inbound Delivery ○

→ Define Document Types for Inbound Delivery Process Using Wizard

○

→ Manual Settings → Define Document Types for Inbound Delivery Process

→ Goods Issue Process → Outbound Delivery ○

→ Define Document Types for Outbound Delivery Process Using Wizard

○

→ Manual Settings → Define Document Types for Outbound Delivery Process

SAP Extended Warehouse Management (SAP EWM)

510

109

SAP Online Help

20.07.2007 ●

●

●

→ Internal Warehouse Processes → Delivery Processing → Posting Changes ○

→ Define Document Types for the Posting Change Process Using Wizard

○

Manual Settings → Define Document Types for Posting Change Process

→ Internal Warehouse Processes → Delivery Processing → Stock Transfers ○

→ Define Document Types for the Stock Transfer Process Using Wizard

○

→ Manual Settings → Define Document Types for the Stock Transfer Process

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

For more information about defining item types in EWM, see the Implementation Guide (IMG) for EWM: ●

●

●

●

●

→ Goods Receipt Process → Inbound Delivery ○

→ Define Item Types for Inbound Delivery Process Using Wizard

○

→ Manual Settings → Define Item Types for Inbound Delivery Process

→ Goods Issue Process → Outbound Delivery ○

→ Define Item Types for Outbound Delivery Process Using Wizard

○

→ Manual Settings → Define Item Types for Outbound Delivery Process

→ Internal Warehouse Processes → Delivery Processing → Posting Changes ○

→ Define Item Types for the Posting Change Process Using Wizard

○

→ Manual Settings → Define Item Types for the Posting Change Process

→ Internal Warehouse Processes → Delivery Processing → Stock Transfers ○

→ Define Item Types for the Stock Transfer Process Using Wizard

○

→ Manual Settings → Define Item Types for the Stock Transfer Process

Services that EWM can use. These include: ○

Text management [Seite 145]

○

Quantity offsetting [Seite 97]

SAP Extended Warehouse Management (SAP EWM)

510

110

SAP Online Help ○

Status management [Seite 94]

○

Field control [Seite 99]

○

Connection to the Post Processing Framework (PPF) [Seite 105]

20.07.2007

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

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

SAP Extended Warehouse Management (SAP EWM)

510

111

SAP Online Help

20.07.2007

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

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

112

SAP Online Help

20.07.2007

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

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

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

Features The common functions that run when creating or changing a warehouse request (either inbound or outbound) automatically, as well as for the inbound delivery and outbound delivery order, enable you to do the following: ●

Automatic Packing EWM automatically creates handling units according to the packing instruction. It uses the condition technique to do this.

●

Connection to SAP Business Information Warehouse When a delivery item has been completed in EWM, EWM sends the current data to SAP Business Information Warehouse. A prerequisite for this is that you must have activated the update of delivery items in SAP Business Information Warehouse. For more information, see the IMG for EWM under Interfaces → SAP Business Information Warehouse → General Settings → Activate BW Update.

The additional functions that run when creating or changing a warehouse request automatically for the inbound delivery, enables you to do the following: ●

If no packaging specification [Extern] exists for the packing of products during goods receipt, EWM can automatically trigger a WebFlow or SAP Alert Framework to notify someone. For this to occur, you must have defined the WebFlow or SAP Alert Framework accordingly. For more information, see the IMG for SCM Basis under Packing → Packaging Specification. For more information about the WebFlow Engine, see the SAP Library under SAP Web Application Server → Business Management (BC-BMT) → WebFlow Engine (BCBMT-WFM). For more information about Alert Management, see the SAP Library under SAP Web Application Server → Basis-Services/Communications Interface (BC-SRV) → Business Workplace and Services (BC-SRV-OFC) → Alert Management (BC-SRV-GBT-ALM).

SAP Extended Warehouse Management (SAP EWM)

510

113

SAP Online Help ●

Determination of a payment for each delivery item

●

Review of the handling unit type for notified handling units

20.07.2007

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

Creation of batches ○

Before you create batches, you must assign a batch class of the class type 023 to the product subject to a batch management requirement in SAP ERP. You have also assigned the object characteristics LOBM_HERKL (country of origin) and LOBM_VFDAT (shelf life expiration date, minimum shelf life) to the batch class. A batch of the product must also exist already in EWM.

○

If the batch is known in ERP, the ERP system sends this information to EWM. EWM automatically provides this in the delivery.

○

If a batch is unknown in EWM, you can specify this batch manually in the inbound delivery.

For more information, see Connection of Delivery Processing to Batch Management [Seite 245]. ●

●

Goods receipt posting ○

If EWM automatically creates a delivery based on a warehouse request from ERP, you can carry out partial goods receipt postings using the warehouse task confirmation. When you confirm a warehouse task, EWM automatically executes a corresponding partial goods receipt posting. It reports this to ERP.

○

With the delivery UI, you can either post the goods receipt for individual handling units only, or you can post it completely.

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

Activities ●

At the same time as an inbound delivery is generated in ERP, ERP sends a message for an inbound delivery notification [Seite 87] or posting change request to EWM.

●

EWM automatically generates a warehouse request using the Post Processing Framework (PPF).

●

During automatic creation and saving of the warehouse request, EWM triggers the following: ○

Mapping of delivery data from ERP onto the EWM delivery data

○

Data enrichment using data from the functions described under Features

○

Wave assignment, depending on your Customizing

○

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

SAP Extended Warehouse Management (SAP EWM)

510

114

SAP Online Help ●

20.07.2007

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

●

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

SAP Extended Warehouse Management (SAP EWM)

510

115

SAP Online Help

20.07.2007

Generation of a Warehouse Request for an Outbound Delivery Order Use Extended Warehouse Management (EWM) uses this function to generate a warehouse request for your goods issue process (outbound delivery request).

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

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

Features The common functions that run when creating or changing a warehouse request (either inbound or outbound) automatically, as well as for the inbound delivery and outbound delivery order, enable you to do the following: ●

Automatic packing EWM automatically creates handling units according to the packing instruction. It uses the condition technique to do this. You can assign handling units and cross-delivery handling units to an outbound delivery order. ERP copies this information to the corresponding ERP outbound delivery.

●

Connection to SAP Business Information Warehouse When a delivery item has been completed in EWM, EWM sends the current data to SAP Business Information Warehouse. As a prerequisite, you must have activated the update of delivery items in SAP Business Information Warehouse. For more information, see the IMG for EWM under Interfaces → SAP Business Information Warehouse → General Settings → Activate BW Update.

The additional functions that run when creating or changing a warehouse request automatically for the outbound delivery order, enables you to do the following: ●

Rough determination of the picking location The system determines the source storage bins for a delivery based on the stock removal strategies. However, it does not make quantity reservations for the products. You can use the activity area that is assigned to the storage bin as a selection criterion.

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

SAP Extended Warehouse Management (SAP EWM)

510

116

SAP Online Help

20.07.2007

For more information about Customizing for stock removal strategies, see the IMG for EWM under Goods Issue Process → Strategies. ●

Determination of which products can be packed together for a shipment

●

Determination of staging area

●

Determination of door assignment

●

Determination of warehouse process type For more information, see the IMG for EWM under Cross-Process Settings → Warehouse Task → Determine Warehouse Process Type.

●

Route determination

●

Determination of staging area group

●

Adding packing items If, for example, you use recyclable packing materials, you can manually add delivery items for the packing material to an outbound delivery order and then post goods issue again for this packing material (see also Processing of Packaging Items [Seite 165]). On the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Maintain Outbound Delivery Order. Select an outbound delivery order, and on the Items tab page, choose with the quick info Create. Use the input help to select a packing item type.

●

You can control processes for outbound delivery orders as part of the configuration. For example, you can create an invoice before goods issue in the outbound delivery process. You can also do this on the basis of other delivery parameters, for example, the export relevance or the route that is determined. As a prerequisite, you have defined process indicators for the delivery document header and for the delivery document items in Customizing for EWM. For more information, see the IMG for EWM under Cross-Process Settings → Delivery Processing → Process Management and Control.

●

You can enter the account assignment on the user interface for the outbound delivery order in the detail view of the item on the Account Assignments tab page.

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

Activities ●

At the same time as an outbound delivery is generated in ERP, ERP sends a message for an outbound delivery request [Seite 90] or posting change request to EWM.

●

EWM automatically generates a warehouse request using the Post Processing Framework (PPF).

●

During automatic creation and saving of the warehouse request, EWM triggers the following: ○

Mapping of delivery data from ERP onto the EWM delivery data

○

Data enrichment using data from the functions described under Features

○

Wave assignment, depending on your Customizing

SAP Extended Warehouse Management (SAP EWM)

510

117

SAP Online Help ○

●

20.07.2007

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

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

●

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

SAP Extended Warehouse Management (SAP EWM)

510

118

SAP Online Help

20.07.2007

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

Prerequisites ●

You have determined the document type for the Post Processing Framework (PPF) action for activating an inbound delivery notification or the outbound delivery request 3 Immediate Processing. You do this in Customizing for the PPF in the action profile in EWM. To do so, in Customizing for Extended Warehouse Management, choose Cross-Process Settings → Delivery Processing → Actions → Change Actions and Conditions → Define Action Profile and Actions. Select the action profile for an inbound delivery notification (/SCDL/IDR) or for an outbound delivery request (SCWM/ODR). Choose Action Definition in the dialog structure and go from there to the Action Definition tab page in the Action Settings screen area for processing time 3 Immediate Processing.

●

In Customizing, you have assigned the defined action profile to a document type. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Goods Receipt Process → Inbound Delivery → Define Document Types for Inbound Delivery Process Using Wizard, or under Goods Issue Process → Outbound Delivery → Define Document Types for Outbound Delivery Process Using Wizard.

●

In the case of inbound deliveries, the status type Warehouse Activities has the status value Not Started in the document. On the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery Order. At header level, check whether the status type Warehouse Activities has the status value Not Started.

●

The following conditions have been fulfilled in the case of outbound deliveries: ○

The status type Warehouse Activities has the status value Not Started in the document. On the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order or Maintain Outbound Delivery. At item level, check whether the status type Warehouse Activities has the status value Not Started for the respective delivery item.

○

The status type Locked (Overall Status) has the status value No in the document. On the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order or Maintain Outbound Delivery. At item level, check whether the staus type Locked (Overall Status) has the status value No.

○

Neither you or the system have assigned a wave [Seite 771] to the delivery item in the document.

SAP Extended Warehouse Management (SAP EWM)

510

119

SAP Online Help

20.07.2007

Process Creating New Documents in EWM ...

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

Inbound Delivery → Maintain Inbound Delivery Notification and the Activate pushbutton.

■

Outbound Delivery → Maintain Outbound Delivery Request and the Activate pushbutton.

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

Inbound Delivery → Maintain Inbound Delivery Notification and the Activate pushbutton.

■

Outbound Delivery → Maintain Outbound Delivery Request and the Activate pushbutton.

Accepting Inbound Delivery Changes to ERP Documents in EWM ...

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

SAP Extended Warehouse Management (SAP EWM)

510

120

SAP Online Help

20.07.2007

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

Accepting Outbound Delivery Changes to ERP Documents in EWM ...

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

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

For more information about document control and processing checked deliveries in the ERP system, see the SAP Library under Documentation → SAP ERP Central Component → SAP ERP Central Component → Logistics → General Logistics (LO) → Service Parts Management: ●

→ Architecture and Communication → document control.

●

→ Goods Issue Process → processing checked deliveries.

See Also: Outbound Delivery Notification [Seite 87] Outbound Delivery Request [Seite 91]

SAP Extended Warehouse Management (SAP EWM)

510

121

SAP Online Help

20.07.2007

Warehouse Request for Internal Stock Transfer Definition This warehouse request defines all warehouse-internal goods movements in Extended Warehouse Management (EWM).

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

122

SAP Online Help

20.07.2007

Internal Stock Transfers Purpose With this warehouse process, you can execute the following warehouse-internal product movements in Extended Warehouse Management (EWM): •

Ad Hoc movement

•

Replenishment

•

Warehouse reorganization

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

Wave Planner

User

SAP WM

Create warehouse request

Create warehouse request

Create transfer order

Release wave

Process transfer order

Confirm transfer order

Confirm transfer order

Close warehouse request

...

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

SAP Extended Warehouse Management (SAP EWM)

510

123

SAP Online Help

20.07.2007

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

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

○

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

124

SAP Online Help

20.07.2007

Executing an Ad Hoc Movement Use You can use this function for the following: ●

An ad hoc decision for a planned stock movement that triggers the creation of a warehouse request.

In the case of a spontaneous decision for a planned stock movement, you can create a warehouse request. You can use this warehouse request in a wave. Once Extended Warehouse Management (EWM) has created the corresponding warehouse task (WT), you can execute the stock movement. ●

An ad hoc decision together with an ad hoc movement that triggers the creation of a WT with immediate, automatic confirmation.

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

125

SAP Online Help

20.07.2007

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

126

SAP Online Help

20.07.2007

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

127

SAP Online Help

20.07.2007

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

Use The warehouse request for posting changes [Extern] is a document that you use in EWM for the following: ●

For planned posting changes, such as a scrapping request, without reference to a posting change request. In other words, for a process triggered inside the warehouse.

●

For unplanned posting changes, such as a scrapping request, with reference to a posting change request. In other words, for a process triggered outside the warehouse. SAP R/3 triggers this when it sends a delivery output to EWM. For more information, see Interfaces for Communication from EWM to the ERP System [Seite 257].

You can also create posting changes directly, without using a warehouse request.

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

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

Automatically by EWM through a PPF action, if you have confirmed the WTs

●

Manually by you in the user interface

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

SAP Extended Warehouse Management (SAP EWM)

510

128

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

129

SAP Online Help

20.07.2007

Performing Scrapping Use You can use this function in the following scenarios: ●

Scrapping within the warehouse, if a product is to be disposed of from the warehouse (for example, defective or obsolete product)

●

Scrapping within a returns process

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

Integration Only scrapping triggered outside the warehouse, such as from the ERP system, is related to a preceding document (delivery request document). For these types of scrapping, Extended Warehouse Management (EWM) sends a delivery output to the ERP system. For scrapping triggered inside the warehouse, EWM sends the following to the ERP system: ●

If you are using SAP ERP 2007, EWM sends a delivery message.

●

If you are using an older SAP ERP release, EWM sends a goods movement message.

Features ●

For warehouse-internal processing of products to be scrapped, you create a warehouse request for the posting change. The system thus posts the products to the blocked stock. From there, you can clear the products through goods issue. EWM can execute the goods issue with or without the corresponding outbound delivery document.

●

EWM processes the scrapping in the returns process with a returns delivery, inspection lots, and inspection results. You can trigger the scrapping warehouseinternally in EWM, or warehouse-externally, for example with SAP Customer Relationship Management. A warehouse worker in the quality department can use an inspection procedure to carry out the decision to scrap a product. Based on the inspection results, he or she can decide whether a product is still to be used or should be scrapped.

Activities ●

You move the products to be scrapped from the different storage bins to a scrapping handling unit (scrapping HU). This represents an internal stock movement that is triggered by the following: ○

Warehouse-internal decision, for example, by a warehouse worker in the quality department

○

Warehouse-external decision when a scrapping message is sent

●

At the same time, EWM posts the quantity to be scrapped as blocked stock. In other words, it carries out a posting change. EWM uses a warehouse request for the posting change for this step. You can use this warehouse request for the posting change during wave creation.

●

You book the goods issue (GI) for the scrapping HU. EWM can execute the GI with the corresponding outbound delivery document. EWM can also execute the GI without a corresponding outbound delivery document. This represents a GI posting without delivery.

SAP Extended Warehouse Management (SAP EWM)

510

130

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

131

SAP Online Help

20.07.2007

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

Use The warehouse request for returns in EWM forms the basis for executing follow-up activities. Follow-up activities for returns include: ●

Reject the inbound delivery after carrying out a rough inspection You first conduct a rough inspection of the inbound delivery. In doing so, if you determine that the forwarding agent does not need to unload the goods, rather can take the goods right back with it because the goods are damaged, for example, you can immediately reject the inbound delivery. On the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Inbound Delivery ○

→ Maintain Inbound Delivery Notification and then Reject

○

→ Maintain Inbound Delivery and then Reject

For more information, see also Goods Receipt [Seite 263]. ●

Putaway [Seite 300]

●

Scrapping [Seite 130]

●

Transferring

●

Delivery to internal remanufacturer

●

Delivery (to customer or external remanufacturer)

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

Create new delivery items

●

Delete delivery items

●

Split delivery items

Structure The structure of a warehouse request for returns differs from the generic structure of a warehouse request as follows: ●

Different item types are used

●

Item category RET is used

●

A different configuration of the item types and the item category is used.

SAP Extended Warehouse Management (SAP EWM)

510

132

SAP Online Help ○

20.07.2007

EWM uses a status profile specifically for the warehouse request for returns: ■

/SCDL/INB_PRD_RET for an inbound delivery

■

/SCDL/INB_REQ_RET for an inbound delivery notification

Thus, EWM can carry out the following: ■

Create the inspection documents automatically (inspection planning)

■

Adjust the status type Q-Inspection automatically when the inspection results are entered The status type Q-Inspection specifies the start and end of the quality inspection.

■

Control the follow-up activities, such as putaway, based on the inspection results SAP CRM determines whether SAP CRM or EWM is to determine followup activities. EWM maps this with status type Blocked According to QM. The status type Blocked After QM specifies that following the quality inspection, the returns stock is blocked from further use until an external system, for example, SAP CRM, makes a usage decision. ●

If status type Blocked According to QM is not set in EWM, you can determine the follow-up activity in EWM. EWM automatically triggers the corresponding logistical processes, such as putaway or returning to the customer.

●

If status type Blocked According to QM is set in EWM, then EWM must first send the inspection result to SAP CRM. After this, SAP CRM determines the follow-up activity and sends it to EWM. EWM triggers the corresponding logistical processes. You can carry out stock transfers in the warehouse during the whole process.

If you carry out a step-by-step inspection in multiple warehouses, then you carry out an individual inspection for each warehouse. If the current warehouse is not the last warehouse in the sequence, EWM sets the status type Blocked QM f. Putaway. Thus, you can only put returns away after the last inspection has been carried out. However, you can scrap or send returns back after each individual inspection. The step-by-step inspection does not affect delivery processing. ○

EWM adopts the effective dates/times from SAP CRM. SAP CRM determines the date and time fort he external and internal validity of the returns and sends this data to EWM. EWM maps the data for external and internal validity to the corresponding date types Internal Validity RMA for Returns and External Validity RMA for Returns and saves them in the delivery item. These date/time types determine whether EWM accepts or rejects returns. ■

If both date/time types have expired, EWM rejects the returns.

■

If the external date/time type has expired, but the internal date/time type is still valid, SAP CRM determines the follow-up activities and decides whether or not to reject the returns. EWM adopts this decision.

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

SAP Extended Warehouse Management (SAP EWM)

510

133

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

134

SAP Online Help

20.07.2007

Processing, Deleting, and Archiving Warehouse Requests Use You can process, delete, or archive warehouse requests.

Features The following table gives you an overview of the functions you can execute for the individual warehouse requests. Object for which EWM creates a warehouse request

Create (manually by user, automatically by EWM)

Process

Delete

Archive

Manually

X

X

X

Automatically

Activation possible only: restricted processing

------

X

Manually

X

X

X

Automatically

X

X

X

Automatically

-----

-----

X

Manually

X

X

X

Automatically

X

X

X

Manually

X (only header data)

X

X

Automatically

-----

-----

X

Posting Change

Manually

X

X

X

Stock Transfer (incl. Scrapping)

Manually

X

X

X

Inbound Delivery Notification

Inbound Delivery

Outbound Delivery Request Outbound Delivery Order

Outbound Delivery

Posting Change Request

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

SAP Extended Warehouse Management (SAP EWM)

510

135

SAP Online Help

20.07.2007

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

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

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

136

SAP Online Help

20.07.2007

Delivery 1

Delivery 2

Delivery 3

10 pcs

HU1

10 pcs

HU2

10 pcs

HU3

20 pcs

HU1

20 pcs

HU3

40 pcs

HU4

30 pcs

HU2

= cross-delivery HU

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

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

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

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

●

On the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Process Outbound Delivery.

SAP Extended Warehouse Management (SAP EWM)

510

137

SAP Online Help

20.07.2007

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

Features User interfaces for the goods receipt process ●

/SCWM/IDN (Maintain Inbound Delivery Notification)

●

/SCWM/PRDI

(Maintain Inbound Delivery)

User interfaces for the goods issue process ●

/SCWM/ODR(Maintain Outbound Delivery Request)

●

/SCWM/PRDO (Maintain Outbound Delivery Order)

●

/SCWM/FD (Maintain Outbound Delivery)

User interfaces for posting changes ●

/SCWM/IM_DR (Maintain Posting Change Request)

●

/SCWM/IM_PC (Maintain Posting Change)

User interfaces for internal stock transfers ●

/SCWM/IM_ST (Maintain Internal Stock Transfer)

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

SAP Extended Warehouse Management (SAP EWM)

510

138

SAP Online Help

20.07.2007

Basic Functions in Delivery Processing Use Delivery processing provides you with the following basic functions: ●

Delivery note printing [Seite 143]

●

Text management [Seite 145]

●

Delivery quantity adjustment [Seite 147]

●

Validation [Seite 159]

SAP Extended Warehouse Management (SAP EWM)

510

139

SAP Online Help

20.07.2007

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

Process ...

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

For more information, see the report documentation.

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

SAP Extended Warehouse Management (SAP EWM)

510

140

SAP Online Help

20.07.2007

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

Prerequisites ●

If appropriate, you have defined a print profile in the default values. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Pickup. Choose Default Values and enter a print profile.

●

If appropriate, you have implemented your own printer determination in Business AddIn (BAdI) /SCDL/PPF_ADD_DATA in method GET_PRINTER. For more information, see the BAdI documentation.

●

If appropriate, you have implemented your own print profile determination in BAdI /SCWM/EX_DLV_PRINT_PROFILE. For more information, see the BAdI documentation.

●

If appropriate, you have defined one or more print profiles in Customizing for EWM. For more information, see the Implementation Guide (IMG) for EWM under Extended Warehouse Management → Goods Receipt Process → Inbound Delivery → Print → Define Print Profiles for Delivery Processing and Goods Issue Process → Outbound Delivery → Print → Define Print Profiles for Delivery Processing.

●

If appropriate, you have defined one or more Post Processing Framework (PPF) actions in Customizing for the PPF. For more information, see the IMG for EWM under Extended Warehouse Management → Cross-Process Settings → Delivery Processing → Actions → Change Actions and Conditions → Define Action Profiles and Actions and Define Conditions.

●

You have defined print profile determination for the goods receipt process or goods issue process in Customizing for EWM. For more information, see the IMG for EWM under Extended Warehouse Management → Goods Receipt Process → Inbound Delivery → Print → Define Print Profile Determination for Goods Receipt Process or Goods Issue Process → Outbound Delivery → Print → Define Print Profile Determination for Goods Issue Process.

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

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

SAP Extended Warehouse Management (SAP EWM)

510

141

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

142

SAP Online Help

20.07.2007

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

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

Features EWM prints the delivery note based on the PPF action /SCWM/PRD_OUT_PRINT for an outbound delivery order or /SCWM/FD_OUT_PRINT for an outbound delivery. ●

By default, EWM uses the predefined SAP Smart Form /SCWM/DLV_NOTE. However, you can also create your own SAP Smart Form to use when printing the delivery note and for form determination.

●

You can also print delivery notes using a PDF-based form. To do this, you must change the assigned processing of the PPF action from Smart Forms Print to External Communication in Customizing for EWM. For more information about action conditions, see the Implementation Guide (IMG) for EWM under Extended Warehouse Management → Cross-Process Settings → Delivery Processing → Actions → Change Actions and Conditions → Define Conditions.

EWM automatically prints the delivery note for an outbound delivery as soon as you have posted the goods issue. You can also use a PPF action to manually print a delivery note for an outbound delivery or outbound delivery order.

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

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

Printing or displaying directly using a PPF action

...

a. On the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Print → Process and Display PPF Actions. b. Specify the document number in the Application Key field. c. Choose

Execute.

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

SAP Extended Warehouse Management (SAP EWM)

510

143

SAP Online Help

20.07.2007

e. Choose

Process.

f. EWM prints the document. ●

Printing or displaying from the user interface of the delivery

...

a. On the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery and then one of the following transactions: ■

Maintain Outbound Delivery Order (/SCWM/PRDO)

■

Maintain Outbound Delivery (/SCWM/FD)

b. Enter the required document number. c. Choose

Change to switch to change mode.

d. Choose the PPF Actions tab page and select the required action (Print Outbound Delivery Order or Print Outbound Delivery). e. Proceed as follows: ■

If you want to display the document, choose

Preview.

EWM displays the document. ■

If you want to print the document, choose

Execute Action.

EWM prints the document.

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

144

SAP Online Help

20.07.2007

Text Management Use With this function, you can do the following to texts belonging to deliveries: ●

Display

●

Change

●

Save

●

Delete

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

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

Prerequisites You have made the Customizing settings for text management [Extern]. ●

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

For more information about defining text types, see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Delivery Processing → Text Management → Define Text Types for Delivery Document Header and Define Text Types for Delivery Document Item. ●

You have defined a text profile [Extern] containing the following: ○

One or more access sequences

○

The assignment of text types to the text profile

○

The assignment of a document or item type to the text profile

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

SAP Extended Warehouse Management (SAP EWM)

510

145

SAP Online Help

20.07.2007

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

Features Text management supports texts: ●

At header level

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

At item level

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

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

Activities ...

To process existing texts or create new ones in SAP EWM, select one of the following: ●

For the goods receipt process, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery Notification or Maintain Inbound Delivery

●

For the goods issue process, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Notification or Maintain Outbound Delivery

●

For posting changes, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Posting Change → Maintain Posting Change Request or Maintain Posting Change

SAP Extended Warehouse Management (SAP EWM)

510

146

SAP Online Help

20.07.2007

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

Prerequisites ●

If you adjust the delivery quantity manually in the user interface of the delivery, the following prerequisites apply: ○

A delivery exists in EWM, which has a status value at item level for status Completion that allows delivery quantity adjustment. That is, it has either status value Not Started or Partially Completed.

○

If you want to use your own process codes, you have defined them in Customizing EWM. For more information, see the IMG for EWM under CrossProcess Settings → Delivery Processing → Process Codes → Define Process Codes.

○

If required, you have assigned the process codes to your own process code profiles in Customizing for EWM. For more information, see the IMG for EWM under Cross-Process Settings → Delivery Processing → Process Codes → Maintain Process Code Profiles.

○

If required, you have assigned the process code profiles to the used document types and items types in Customizing for EWM. For more information, see the IMG for EWM at the following locations:

○

■

Goods Receipt Process → Inbound Delivery → Manual Settings → Define Document Types for Inbound Delivery Process or Define Item Types for Inbound Delivery Process

■

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

■

Internal Warehouse Processes → Delivery Processing → Posting Changes → Define Document Types for the Posting Change Process or Define Item Types for the Posting Change Process

For the availability check, you have not defined any of the following restrictions for the quantity increase in Customizing for EWM. For more information, see the IMG for EWM under Interfaces → Availability Check → Define Configuration of Availability Check. ■

Under Allowed Quantity Increase, you have not defined A Quantity Increase Not Allowed, meaning that the quantity increase is generally not allowed for the party entitled to dispose, item type, product group type, and product group.

■

Under Allowed Quantity Increase, you have not defined B Special Authorization Required to Increase Quantity, meaning that the user who wants to execute the quantity increase requires authorization for activity 94 (Override) for authorization object /SCWM/DLV.

SAP Extended Warehouse Management (SAP EWM)

510

147

SAP Online Help

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

●

If you adjust the delivery quantity using an exception code for an automatic delivery update, you must also have defined exception codes in Customizing for EWM and assigned them to the process codes. For more information, refer to the IMG for EWM under Cross-Process Settings → Exception Handling → Define Exception Codes.

●

For both types of delivery quantity adjustment, you have also assigned partner roles to the process codes in Customizing for EWM under Cross-Process Settings → Delivery Processing → Process Codes → Define Process Codes. If you record quantity differences for stock transfer orders [Seite 150] for example, the partner you define here corresponds to the person who caused the delivery quantity difference. EWM saves delivery quantity differences for this partner and sends the information to the ERP system. The only information EWM does not send to ERP is information about delivery quantity differences for posting change deliveries,since these involve internal warehouse differences.

●

For both types of delivery quantity adjustment, you have also defined in Customizing for EWM the partners for which EWM reports exceptions, namely process codes, to ERP. For more information, see the IMG for EWM under Interfaces → ERP Integration → Delivery Processing → Map Partner Roles from ERP System to EWM.

Features EWM considers the following quantities for delivery quantity adjustment: ●

In the inbound delivery, EWM considers the quantities for goods receipt, packing, and planned putaway, meaning EWM matches the delivery quantity to the largest of these quantities.

●

In the outbound delivery order, EWM considers the quantities for loading, packing, and planned picking, meaning EWM matches the delivery quantity to the largest of these quantities.

●

In the posting change delivery, EWM considers the quantity for planned internal movements, meaning EWM matches the delivery quantity to this quantity.

In Customizing for the process code, you can define one of the following types for the delivery quantity adjustment: ●

EWM does not adjust the delivery quantity, although EWM saves a process code in the delivery that you can also view in the respective user interface of the delivery.

●

EWM adjusts the delivery quantity and saves a process code in the delivery.

●

EWM adjusts both the delivery quantity and the transferred delivery quantity, meaning EWM performs a delivery split in the goods receipt process or goods issue process. EWM also saves a process code in the delivery.

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

Activities You can adjust delivery quantities in one of the following ways: ●

On the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing and then the corresponding user interface: ○

Inbound Delivery → Maintain Inbound Delivery

○

Outbound Delivery → Maintain Outbound Delivery Order

SAP Extended Warehouse Management (SAP EWM)

510

148

SAP Online Help ○

20.07.2007

Posting Change → Maintain Posting Change.

You adjust the delivery quantity manually in the user interface of the delivery. ●

If you are confirming a warehouse task or recording counting, on the SAP Easy Access screen choose Extended Warehouse Management → Execution → Confirm Warehouse Task or Execution → Quality Inspection and Count, to specify an exception code. EWM assigns this exception code to a process code, corresponding to the settings you have made in Customizing. EWM then uses the delivery update to adjust the delivery quantity for each item, corresponding to the settings of the process code.

●

If you are repacking delivery stock, on the SAP Easy Access screen choose Extended Warehouse Management → Execution → Packing - General. If you have defined the work center correspondingly in Customizing for EWM, then EWM displays the tab page Differences. For this, you have defined the work center layout in the IMG for EWM under Master Data → Work Center → Specify Work Center Layout. You record the difference and specify an exception code. EWM maps this exception code to the relevant process code in the background and updates the delivery.

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

SAP Extended Warehouse Management (SAP EWM)

510

149

SAP Online Help

20.07.2007

Quantity Differences for Stock Transfer Orders Purpose In Extended Warehouse Management (EWM), you can confirm stock transfer orders with a quantity difference. This enables you to map the following processes: ●

You receive a quantity shortage or quantity excess in the inbound delivery, which was caused by a delivering warehouse; for example, the delivering warehouse has not loaded a pallet onto the vehicle.

●

You receive a quantity shortage or quantity excess in the inbound delivery, which was caused by a carrier; for example, a carrier damaged the goods.

●

In cross-docking [Seite 544], you can confirm quantity excesses or shortages that were caused by the first cross -docking warehouse and not the delivering warehouse.

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

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

Prerequisites ●

You are working in a system landscape that includes an ERP system, central SAP Advanced Planning & Optimization (SAP APO) for the automatic generation of stock transfer orders, and at least one decentralized EWM.

●

You are using interfaces between EWM and the ERP system. For more information, see Communication from EWM to ERP System [Seite 248].

●

You have defined tolerance groups for the Difference Analyzer in the Customizing settings for EWM. For more information, see the Implementation Guide (IMG) for EWM under Internal Warehouse Processes → Physical Inventory → Warehouse-Number-Specific Settings → Define Tolerance Groups → Define Tolerance Group for Difference Analyzer.

●

You have assigned the user to a tolerance group for the Difference Analyzer in the Customizing settings for EWM. To do so, on the SAP Easy Access screen, choose

SAP Extended Warehouse Management (SAP EWM)

510

150

SAP Online Help

20.07.2007

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

EWM in the Source Warehouse ●

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

Make sure that the Customizing settings for EWM for your own document types and for the item types used are correct. If you are defining your own profiles, use the delivered document types and item types and their relevant profiles as a basis. ●

You have defined the mapping of the document types from the ERP system in EWM in Customizing for EWM. For more information, see the IMG for EWM under Interfaces → ERP Integration → Delivery Processing → Map Document Types from ERP System to EWM System.

EWM in the Target Warehouse ●

In Customizing for EWM, you have defined whether EWM is to execute an automatic or manual goods movement. For more information, see the IMG for EWM, under Cross-Process Settings → Delivery Processing → Actions → Use Assistant to Create Actions.

●

In Customizing for EWM, you have defined process codes and assigned these to your own process code profiles. You have also assigned partner roles to the process codes (see Delivery Quantity Adjustment [Seite 147]).

●

You have defined the mapping of the exception code to the process code of the delivery processing in Customizing for EWM. For more information, refer to the IMG for EWM under Cross-Process Settings → Exception Handling → Define Exception Codes.

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

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

510

151

SAP Online Help

20.07.2007

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

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

SAP Extended Warehouse Management (SAP EWM)

510

152

SAP Online Help

20.07.2007

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

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

SAP Extended Warehouse Management (SAP EWM)

510

153

SAP Online Help

20.07.2007

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

Prerequisites ●

You have defined process codes that adjust both the delivery quantity and the transferred delivery quantity [Extern], that is, you have chosen the value 2 Adjustment of Delivery Quantity and Del. Quant. Transferred for the quantity adjustment. For more information, see the Implementation Guide (IMG) under Extended Warehouse Management → Cross-Process Settings → Delivery Processing → Process Codes → Define Process Codes.

●

You defined process code profiles. If Extended Warehouse Management (EWM) is to use a default process code (for example, /002) for quantity changes, you have chosen a default process code in the Customizing settings. For more information, see the IMG under Extended Warehouse Management → Cross-Process Settings → Delivery Processing → Process Codes → Maintain Process Code Profiles.

●

You have defined the item types for the inbound deliveries in which you assigned the corresponding process code profiles. For more information, see the IMG under Extended Warehouse Management → Goods Receipt Process → Inbound Delivery → Manual Settings → Define Item Types for Inbound Delivery Process.

●

Either you or the system can split delivery items or partial quantities into a new delivery. The prerequisite for this is that you have not performed a warehouse activity for this delivery item or partial quantity. For example, you have not posted the goods receipt (GR) yet.

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

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

SAP Extended Warehouse Management (SAP EWM)

510

154

SAP Online Help

20.07.2007

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

the quantities of the open warehouse tasks

●

the packed quantity

●

the GR posted quantity

●

the unloaded quantity

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

Example Example for a Manual Delivery Split ...

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

SAP Extended Warehouse Management (SAP EWM)

510

155

SAP Online Help

20.07.2007

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

Prerequisites Prerequisites for the Outbound Delivery Order Split Based on the Outbound Delivery Request ●

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

Prerequisites for the Outbound Delivery Order Split ●

You have defined process codes that adjust both the delivery quantity and the transferred delivery quantity, that is, you have chosen the value 2 Adjustment of Delivery Quantity and Del. Quant. Transferred for the quantity adjustment. For more information, see the IMG for EWM under Cross-Process Settings → Delivery Processing → Process Codes → Define Process Codes.

●

You defined process code profiles. If EWM is to use a default process code (for example, O002) for quantity changes, you have chosen a default process code in the Customizing settings. For more information, see the IMG for EWM under CrossProcess Settings → Delivery Processing → Process Codes → Maintain Process Code Profiles.

●

You have defined the item types for the outbound deliveries in which you assigned the corresponding process code profiles. For more information, see IMG for EWM under Goods Issue Process → Outbound Delivery → Manual Settings → Define Item Types for Outbound Delivery Process.

●

Either you or the system can split delivery items or partial quantities into a new delivery. The prerequisite for this is that you have not performed a warehouse activity for this delivery item or partial quantity. For example, you have not created a warehouse task for picking yet.

Prerequisites for the Outbound Delivery Split ●

If the delivery item of the outbound delivery is relevant for picking, you have at least picked the delivery quantity that you want to split into a new subitem. You can only create new subitems for this picked quantity.

●

If you have already started loading, that is, the status type Loading for the delivery item has the status value Partially Completed, the delivery quantity that you have split must

SAP Extended Warehouse Management (SAP EWM)

510

156

SAP Online Help

20.07.2007

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

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

Outbound Delivery Order Split The same functions exist for the outbound delivery order split as for the Delivery Split for Inbound Deliveries [Seite 154]. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order. However, when EWM adjusts the delivery quantities, it takes different quantities into account than for the delivery split for inbound deliveries. EWM takes the following quantities of the outbound delivery order into account: ●

The quantities of the open warehouse tasks

●

The packed quantity

●

The loaded quantity

●

The aggregated quantity

●

The picked quantity

●

The number of serial numbers

●

The catch weight quantity assignment

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

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

SAP Extended Warehouse Management (SAP EWM)

510

157

SAP Online Help

20.07.2007

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

Activities for the Outbound Delivery Split On the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order. ●

If you want to split a delivery item for unpacked products, perform the following steps:

...

a. Go to the Items tab page and select a delivery item. b. Choose the arrow on the right-hand side of Subitem and then choose Split Up Outbound Delivery. c. Specify the number of subitems that are to be created. EWM creates one or more new subitems for which you can specify the desired delivery quantity. d. Choose

with the quick info Save.

EWM saves the new subitem, thus splitting the delivery item. e. Choose

with the quick info Create Outbound Delivery.

EWM creates an outbound delivery for the subitem. ●

If you want to split a delivery item for packed products, perform the following steps:

...

a. Go to the HU tab page and select an HU item. b. Choose the arrow Create.

on the right-hand side of Split Item and then choose

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

with the quick info Save.

EWM saves the new subitem, thus splitting the delivery item. d. Choose

with the quick info Create Outbound Delivery.

EWM creates an outbound delivery for the subitem. ●

If you want to undo a delivery item split, perform the following steps:

...

a. Go to the Items tab page. b. Delete the corresponding outbound delivery first by selecting the outbound with quick info Delete. delivery and choosing ■

If you want to delete the subitem of an unpacked product, select the subitem and choose with the quick info Delete. EWM totally deletes the subitem.

■

If you want to delete the subitem of a packed product, undo the HU split. Go to the HU tab page and select the subitem. Choose the arrow on the right-hand side of Split Item and then choose Undo. EWM totally deletes the subitem.

SAP Extended Warehouse Management (SAP EWM)

510

158

SAP Online Help

20.07.2007

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

159

SAP Online Help

20.07.2007

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

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

Features A process indicator has multiple values, for example process indicator Scrapping has the value Not Allowed and Required. A process indicator describes the entire business transaction represented by the delivery document. For the document header and document item, SAP delivers a set of process indicators in the system profile and customer profile of process control. The process indicators are linked to the document and item types of delivery processing via a process profile. You can change the settings for the process indicators in the process profile. When Extended Warehouse Management (EWM) creates a delivery document, the system sets the process indicator. You can then no longer make changes to these. However, if you have set the value Allowed for process indicator IBGI (invoice creation before goods issue) in Customizing for EWM, under Cross-Process Settings → Delivery Processing → Process Management and Control → Define Process Profile for Delivery Document, you can change the value of this process indicator in a direct outbound delivery order. However, you can only do this as long as the outbound delivery has not yet been created. You can choose from the following process indicators: Process Indicator

Meaning

Manual creation

Use Certain deliveries, such as direct outbound delivery orders and posting changes, can be created and processed in EWM directly. They do not require a preceding document in ERP.

Preceding document

Allows a reference to a preceding document (purchase order, sales order, or production order)

Inbound and outbound deliveries usually have a reference to a preceding document, inbound deliveries for purchase orders, and outbound deliveries for sales orders. Posting changes or outbound deliveries without reference, on the other hand, do not refer to a preceding document.

Production

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

If inbound and outbound deliveries are used in a production process, you have a reference to a production

SAP Extended Warehouse Management (SAP EWM)

510

160

SAP Online Help

20.07.2007 production

order.

Scrapping

Allows subprocesses for scrapping

In the scrapping process, you perform a planned reduction of overstock in two steps: you first post change the stock to locked stock, and then post the locked stock.

Pickup

Allows a process for direct sales

In this process, you only make goods available for the sales location within the warehouse. You do not perform any transportation activities.

Invoice Creation Before Goods Issue

Allows invoice creation before goods issue

You can create the invoice in the early stages of the process flow within the packing or loading goods process step.

Correction delivery

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

If you identify warehouseexternal differences, e.g. in a stock transfer process or for a customer delivery, which require warehouse stock to be corrected, you can post these to the stock of the differences to be cleared using a correction delivery.

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

SAP Extended Warehouse Management (SAP EWM)

510

161

SAP Online Help

20.07.2007

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

Prerequisites ●

The goods movement bin in the warehouse request from which you are booking out the stock for the goods issue must contain a valid storage bin in which a sufficient quantity of the product is available.

●

You use an item type that does not contain any of the following status types in the status profile: ○

Planned Picking

○

Picking

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

Process ...

1. You or EWM create the warehouse request for an outbound delivery order. Either ERP distributes an outbound delivery to EWM and EWM automatically generates a corresponding warehouse request, or you manually generate the warehouse request in EWM as a direct outbound delivery order [Seite 167]. You specify all the relevant stock attributes of the product (for example, the stock type) and a goods movement bin in the warehouse request. ○

If you have configured goods movement bin determination, EWM automatically suggests a goods movement bin. On the SAP Easy Access screen, choose Extended Warehouse Management → Settings → Maintain Goods Movement Bin Determination. EWM also uses the settings that you specify here to process inbound deliveries that are not relevant to putaway.

○

If you generate the warehouse request manually, choose one of the following options: ■

You specify the items with their stock attributes and quantities on the Items tab page.

■

On the HU tab page, you choose the Create and Save pushbuttons and specify a handling unit (HU) and an item type. Then EWM automatically creates the corresponding items with their stock attributes and quantities.

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

SAP Extended Warehouse Management (SAP EWM)

510

162

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

163

SAP Online Help

20.07.2007

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

Prerequisites ●

The goods movement bin in the warehouse request into which you are booking the stock for the goods receipt must contain a valid storage bin into which you can book the product.

●

You use an item type that does not contain any of the following status types in the status profile: ○

Planning Putaway

○

Putaway

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

Process ...

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

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

SAP Extended Warehouse Management (SAP EWM)

510

164

SAP Online Help

20.07.2007

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

Prerequisites ●

The product of the packaging item is a packaging material. Check the settings for the packaging data in the global view of the product master. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Product → Maintain Product and then choose the Global Data setting in the View group box. Choose the Pkg Data tab page and display the relevant data.

●

In the goods issue process, the goods movement bin in the warehouse request from which you are booking out the stock for the goods issue must contain a valid storage bin in which a sufficient quantity of the product is available.

Process ...

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

SAP Extended Warehouse Management (SAP EWM)

510

165

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

166

SAP Online Help

20.07.2007

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

Use Unlike EWM outbound delivery orders, for which ERP generated a reference document previously, you or EWM can also generate direct outbound delivery orders directly and locally in EWM, which EWM then sends to ERP. You can use direct outbound delivery orders in the following scenarios: ●

Pickup [Extern] ○

Direct sales For direct sales, transportation activities do not apply, since the customer asks for the goods and picks them up on-site in the warehouse. You do not need to create a sales order for this. The direct outbound delivery order you generated manually in EWM forms the basis for the delivery in ERP. The delivery in ERP forms the outbound document for billing. You can also trigger direct sales in ERP without generating a sales order.

○

Account assignment For account assignment, transportation activities also do not apply, since the internal or external customer asks for the goods and picks them up on-site in the warehouse. Unlike for direct sales, you post a goods issue with account assignment for the goods, for the cost center, for example. You can also trigger goods issue with account assignment in ERP without generating a sales order.

●

Scrapping [Seite 366] The Direct Outbound Delivery Order for Scrapping [Seite 175] forms the last step in the scrapping process. You post the goods to be scrapped with the goods issue from the warehouse stock. Whereas you can also trigger the preparation for scrapping – such as collecting goods in a scrapping container – using a posting change request from ERP, you always trigger this last step locally in the warehouse.

●

Immediate Delivery (Push or Pull Procedure) [Seite 172]

●

Kit to stock or reverse kitting For kit to stock, you use a value-added service order [Extern] to create a kit from different components. If you want to reserve the corresponding components, you can use a direct outbound delivery order. When you have created the kit and post goods issue for the direct outbound delivery order, EWM reduces the stock of the respective components. You can use the direct outbound delivery order to execute actions that you require for generating and processing an outbound delivery in the warehouse, such as picking. You can carry out the following for a direct outbound delivery order: ○

Save

SAP Extended Warehouse Management (SAP EWM)

510

167

SAP Online Help

20.07.2007

○

Validate

○

Archive

○

Delete

Structure For the structural description of the direct outbound delivery order, see Outbound Delivery Order [Seite 91]. The structure of a direct outbound delivery order also contains the following, differentiating it from the structure of an outbound delivery order: ●

Document categories with different document types You can define the document types in Customizing for delivery processing.

For more information about defining document types in EWM, see the Implementation Guide (IMG) for EWM under Goods Issue Process → Outbound Delivery:

●

■

→ Define Document Types for Outbound Delivery Process Using Wizard

■

→ Manual Settings → Define Document Types for Outbound Delivery Process

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

For more information about defining item types in EWM, see the Implementation Guide (IMG) for EWM under Goods Issue Process → Outbound Delivery: ■

→ Define Item Types for Outbound Delivery Process Using Wizard

■

→ Manual Settings → Define Item Types for Outbound Delivery Process

Direct outbound delivery orders have the following properties that differentiate them from outbound delivery orders that were generated in EWM based on outbound deliveries created in ERP: ●

Necessity of the availability check, as this check is usually triggered in ERP To avoid endangering the continual ability to deliver, the planning situation must be adjusted with the availability check.

In SAP SCM 5.1, planning-related reservation of the products only takes place if you are using SAP Advanced Planning and Optimization (SAP APO). No reservation takes place for checks in ERP. In exceptional cases, overconfirmation may occur. ●

A lot of organizational and logistically relevant delivery data that is copied to outbound delivery orders from ERP preceding documents must be specified for the direct outbound delivery orders locally in EWM. Either you enter the data directly, such as the product or quantity, or EWM determines the data automatically using configuration data, such as the goods issue bin for items that are not pick-relevant. As you start the goods issue process using direct outbound delivery orders in EWM, the underlying document type must display the process correspondingly. EWM uses the process profile to do this. When generating a direct outbound delivery order, you must select the correct document type to ensure the process flow is correct. For more

SAP Extended Warehouse Management (SAP EWM)

510

168

SAP Online Help

20.07.2007

information, see the IMG for EWM under Cross-Process Settings → Delivery Processing → Process Management and Control. ●

As no outbound delivery request from ERP exists for direct outbound delivery orders, actions such as splitting direct outbound delivery orders are not possible (see Delivery Split for Outbound Deliveries [Seite 156]). Direct outbound delivery orders are also always checked, meaning they have the status type Locked (Unchecked Item) and statusvalue No, and are immediately ready for processing.

●

Direct outbound delivery orders support processing of non-pick-relevant items, for example, or generation of items from handling units.

Integration ●

As direct outbound delivery orders are created in EWM directly, no availability check is performed in ERP for the required product. Instead, EWM triggers the availability check. Depending on the configuration, the check can be performed in ERP or in SAP APO. For outbound delivery orders replicated from ERP, however, the availability check is triggered in ERP. For more information, see Availability Check [Seite 176].

●

EWM can send direct outbound delivery orders for scrapping to ERP. Prerequisite for this is that you are using the corresponding Enhancement Package of ERP. For more information, see the Implementation Guide (IMG) for EWM under Interfaces → ERP Integration → General Settings → Set Control Parameters for ERP Version Control. If you are not using a corresponding Enhancement Package, only the goods movement posting takes place. There is no delivery replication.

●

When you generate a direct outbound delivery order, EWM automatically performs a Compliance Check [Seite 222].

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

SAP Extended Warehouse Management (SAP EWM)

510

169

SAP Online Help

20.07.2007

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

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

Prerequisites ●

You are using the corresponding ERP Enhancement Package. Only then does EWM give information about direct outbound delivery orders and perform an availability check. For more information, see the Implementation Guide (IMG) for EWM under Interfaces → ERP Integration → General Settings → Set Control Parameters for ERP Version Control.

●

You have assigned sales organizations. In the SAP Easy Access menu, choose Extended Warehouse Management → Interfaces → GTS: Assign Sales Organization.

●

If you want EWM to perform automatic determination of the goods movement bin for delivery items that are not pick-relevant, you have defined the goods movement bin determination. EWM defines the goods movement bin depending on the following: ○

Document type

○

Item type

○

Warehouse number

○

Combination of the two product master attributes product group type and product group

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

Features For direct outbound delivery orders, all the functions are available to you that you can perform for outbound deliveries. The following list describes the additional functions or functions that vary: ●

You can also use direct outbound delivery orders for goods issue in the scrapping process (see Performing Scrapping [Seite 130]).

●

You can delete a direct outbound delivery order in EWM. EWM only sends a deletion message for direct outbound delivery orders to ERP.

●

You can add new delivery items with reference to a reference document to a direct outbound delivery order. EWM sends these added delivery items to ERP, and ERP copies these to the relevant ERP outbound delivery. An availability check is also performed for the added items (see Availability Check [Seite 176]).

●

If you want to increase the outbound delivery quantity of an item manually, and ERP has already generated an item for this in the ERP outbound delivery, EWM does not

SAP Extended Warehouse Management (SAP EWM)

510

170

SAP Online Help

20.07.2007

perform another availability check for the difference quantity. When you generate a new item or direct outbound delivery order, EWM can perform an availability check for this quantity. ●

If you want to reduce the outbound delivery quantity, you can do this directly in the direct outbound delivery order. In this case, no further availability check takes place. Only when ERP copies the quantity change into the ERP outbound delivery does SAP Advanced Planning and Optimization (SAP APO) adjust its planned quantity.

●

When you generate a direct outbound delivery order from the user interface of the outbound delivery order, you can manually assign stock to a delivery item that does not have a picking status. Display your direct outbound delivery orders in the form view of the user interface of the outbound delivery order. Choose the input help for Goods Mvt Bin and look for a bin in which stock exists.

Constraints in ERP ●

You cannot use credit management for direct outbound delivery orders.

●

The price determination in ERP does not provide you with the same functions as the price determination in the sales order.

●

You cannot use any configurable products in direct outbound delivery orders.

●

You cannot perform billing in SAP Customer Relationship Management (SAP CRM) for direct outbound delivery orders.

●

You cannot extend bills of materials in direct outbound delivery orders.

●

ERP does not send messages for a direct outbound delivery order to EWM.

Constraints in EWM ●

If you are adding packing items to a direct outbound delivery order, EWM cannot perform an availability check for these new delivery items.

●

The kit-to-order process does not support direct outbound delivery orders.

●

Direct outbound delivery orders are not relevant for backorder processing in SAP APO.

SAP Extended Warehouse Management (SAP EWM)

510

171

SAP Online Help

20.07.2007

Fulfilling Immediate Deliveries with Direct Outbound Delivery Orders Purpose You can fulfill immediate deliveries and choose between a push and pull procedure: ●

In the push procedure, you make a decision for the outbound delivery without a sales order from the current requirements of the warehouse. For example, you want to use your available transportation capacities as optimally as possible by making use of unused space in a vehicle. Or you have to consider the special requirements of the consumer products industry. For example, you want to distribute a very recent delivery containing fresh goods (lettuce) to outbound deliveries going to different stores.

●

In the pull procedure, the store or customer triggers the process. For example, you only notice later that an article in the last purchase order was not included. You call the warehouse and trigger immediate delivery, so that the goods still delivered on time.

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

172

SAP Online Help

20.07.2007

Pull Procedure

Push Procedure

Customer / Store

Warehouse

Check stock and purchase orders

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

ii.

Choose the function

Search.

EWM displays all the expected goods receipts it finds in the lefthand area of the screen. iii.

In the lefthand screen area, set Flag for a delivery item in the expected goods receipt.

iv.

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.

Select the Inbound Delivery under Find and specify the document number of the inbound delivery.

ii.

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

20.07.2007

i.

Select the Purchase Order under Find and specify the document number of the purchase order.

ii.

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.

In the lefthand screen area, set Flag for a delivery item in the expected goods receipt.

iv.

Copy Flagged Item, and choose Choose to the right of the function Add Flagged Item to Inbound Delivery. EWM displays a dialog box containing numerous document numbers of the two search queries.

v.

Select the document number you require by choosing

Copy.

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

Save and save the new inbound delivery item.

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

SAP Extended Warehouse Management (SAP EWM)

510

190

SAP Online Help

20.07.2007

Goods Receipt Posting from Production Purpose In Extended Warehouse Management (EWM), you can post goods receipt for your finished products.

Process If you want to post goods receipt from production, you have the following options: ●

Goods Receipt Posting Triggered by ERP [Seite 192]

●

Goods Receipt Posting Triggered by EWM [Seite 195]

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

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

SAP Extended Warehouse Management (SAP EWM)

510

191

SAP Online Help

20.07.2007

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

Prerequisites ●

You are using SAP SCM 5.1 and the corresponding ERP release. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Interfaces → ERP Integration → General Settings → Set Control Parameters for ERP Version Control.

●

You are using simple transport routes, for example without stock transport orders, so that your goods receipt posting in the central warehouse directly triggers generation of the EWM inbound delivery in the decentralized warehouse.

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

SAP Extended Warehouse Management (SAP EWM)

510

192

SAP Online Help

20.07.2007

ERP (Delivery)

EWM

ERP (Production)

1

User generates production order

1

User releases production order

Confirmation of production end triggers goods receipt posting

3

3

System generates inbound delivery

System posts goods receipt

System updates production order and inbound delivery

2 User confirms production steps and 3 production end

4 System generates inbound delivery

7 User posts goods receipt

7 User puts away product

6

User transports product to warehouse

5

6

...

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

○

Implementation Guide (IMG) for ERP: ■

Production → Production Control → Master Data → Define Production Scheduling Profile

■

Production → Basic Data → Routing → Operation Data → Define Control Key

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

SAP Extended Warehouse Management (SAP EWM)

510

193

SAP Online Help

20.07.2007

○

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

○

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

194

SAP Online Help

20.07.2007

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

Prerequisites ●

You are using SAP SCM 5.1 and the corresponding ERP release. For more information, see the Implementation Guide (IMG) for EWM under Interfaces → ERP Integration → General Settings → Set Control Parameters for ERP Version Control.

●

You are using simple transport routes, for example without stock transport orders, so that your goods receipt posting in the central warehouse directly triggers generation of the EWM inbound delivery in the decentralized warehouse.

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

SAP Extended Warehouse Management (SAP EWM)

510

195

SAP Online Help

20.07.2007

ERP (Delivery) User generates production order

User releases production order

Function module generates new expected goods receipts (GRs)

EWM

1

2 Report call deletes expected GRs

System generates expected GRs

System generates inbound delivery

System posts goods receipt

System updates production order and inbound delivery

ERP (Production)

1

6

8

8

User generates inbound delivery as copy of expected GR

User posts goods receipt

User puts away product

2

3

6

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

7

7

...

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

SAP Extended Warehouse Management (SAP EWM)

510

196

SAP Online Help

20.07.2007

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

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

SAP Extended Warehouse Management (SAP EWM)

510

197

SAP Online Help

20.07.2007

Connection of Delivery Processing to Additional Functions Use Delivery processing uses the following additional functions: ●

Connection to yard management [Seite 199]

●

Connection to transportation management [Seite 201]

●

Connection to route determination [Seite 202]

●

Connection to serial numbers [Seite 213]

●

Connection to SAP Global Trade Services (SAP GTS) [Seite 214]

●

Connection to Environment, Health & Safety (EH&S) [Seite 967]

●

Connection to determination of country of origin [Seite 224]

●

Connection to the Post Processing Framework [Seite 226]

●

Connection to value-added service order (VAS order) [Seite 230]

●

Kit in the warehouse request for the outbound delivery order [Seite 234]

●

Connection to quality management [Seite 293]

●

Connection to batch management [Seite 245]

SAP Extended Warehouse Management (SAP EWM)

510

198

SAP Online Help

20.07.2007

Connection of Delivery Processing to Yard Management Use If you use yard management [Seite 619] in Extended Warehouse Management (EWM), this communicates with delivery processing to exchange relevant information such as status changes. This enables delivery processing to allow follow-up actions, such as statusdependent goods receipt posting. Yard management and delivery processing exchange the following information changes: ●

Status changes in the delivery, such as from In transit to In yard

●

Information about transportation units (TUs)

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

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

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

EWM writes this TU data to delivery processing and the handling unit in the following way: ●

If shipping and receiving is activated, delivery processing changes the status value for the Assign Transportation Unit status of the delivery document item from Not relevant to Not started.

●

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

SAP Extended Warehouse Management (SAP EWM)

510

199

SAP Online Help

20.07.2007

■

Delivery document header status In yard or Outside yard

■

Vehicle

■

Door

d. As soon as the Assign Transportation Unit status of the delivery document header has the value In processing or Completed, delivery processing locks the delivery document for assigning transportation units. It then informs yard management about this lock and the status changes that have occurred. This lock prevents data inconsistencies occurring between delivery processing and yard management. Now you can only change the assignment of transportation units in shipping and receiving or in yard management. ●

Using an action for the transportation unit If you execute actions for transportation units, such as Loading Begin, EWM simultaneously updates the delivery documents and handling units that are assigned. In delivery processing, you can only execute the actions In Yard or Leave Yard for transportation units that are assigned to the respective delivery documents or vehicles. To keep the data consistent, EWM distributes the assignment of transportation units to doors using the delivery documents and handling units that are assigned.

See also: Assignment of Deliveries to Vehicles and TUs [Seite 617]

SAP Extended Warehouse Management (SAP EWM)

510

200

SAP Online Help

20.07.2007

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

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

SAP Extended Warehouse Management (SAP EWM)

510

201

SAP Online Help

20.07.2007

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

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

Prerequisites ●

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

●

The following delivery data has been specified: ○

The supply chain unit of the warehouse at the delivery header Route determination uses this supply chain unit as a source location.

○

At least one item with an entry for product, a quantity, weight and volume

○

At least one item with a planned goods issue date (for forwards scheduling) or a planned delivery date at header level (for backwards scheduling)

○

If you are using your own document types, the route status must be activated at header level so that route determination can set this status.

○

If the following delivery data is available, route determination uses it as an additional constraint during route determination: ■

The carrier, if the determination indicator [Extern] is not initial or the carrier has been specified by EWM.

■

The means of transport, if the determination indicator is not initial or the means of transport has been specified by EWM.

■

The route itself, if the determination indicator is not initial or the route has been specified by EWM.

■

The shipping conditions of all items, if all the items have the same shipping conditions.

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

SAP Extended Warehouse Management (SAP EWM)

510

202

SAP Online Help

20.07.2007

SAP Customer Relationship Management (SAP CRM) assigns a route to EWM. Route determination in the delivery does not overwrite any routes manually entered. You define the route determination status in Customizing for EWM: ●

Route Determination is Always Active ().

●

Automatic Route Determination Only in Case of Initial Route

●

Automatic Route Determination Inactive

●

Route Determination Inactive

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

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

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

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

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

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

203

SAP Online Help

20.07.2007

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

204

SAP Online Help

20.07.2007

Making Settings for Route Determination To use route determination, you must make the following settings:

Customizing ●

You have activated the route determination of transportation management in Customizing in Extended Warehouse Management (EWM). For more information, see the Implementation Guide (IMG) for EWM under Goods Issue Process → Transportation Management → Route Determination → General Settings for Route Determination.

●

You have activated the route determination for the delivery or the warehouse that is being used. For more information, see the IMG for EWM under Goods Issue Process → Outbound Delivery → Route Determination → Activate or Deactivate Route Determination.

●

You also have the option of making additional settings for scheduling. For more information, see the IMG for EWM under Goods Issue Process → Outbound Delivery → Route Determination → Define Scheduling Within Route Determination.

Master Data ●

You have created a route and a leg from the supply chain unit [Extern] of the sending warehouse (source location) to the supply chain unit of the recipient (ship-to location). Here, the destination location may also be a zone. To do this, on the SAP Easy Access screen, you have chosen Extended Warehouse Management → Master Data → Shipping and Receiving → Route Determination → Maintain Route.

●

You have made sure that the goods recipient in the delivery has been assigned to a supply chain unit that is being used for route determination. As a business partner or address is entered in the delivery as a goods recipient, an assignment still has to be made with which the destination location used in a route is determined. This is done in the following way: ○

If a document address is entered in the delivery for the goods recipient, the system attempts to find a supply chain unit zone based on the address data. This zone is then used as the destination location for route determination.

○

If no document address is used, a corresponding supply chain unit is found in the following way: If you are working without an address or without a zone as a destination location in the route, you have created an individual supply chain unit for the ship-to party in the supply chain unit master data. In the Bus.Partner field on the General tab page, you assign this supply chain unit to the business partner (ship-to party) that has been entered in the delivery.

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

SAP Extended Warehouse Management (SAP EWM)

510

205

SAP Online Help

20.07.2007

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

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

If EWM finds one distinct entry, it uses this supply chain unit.

○

If EWM does not find an assignment, it checks whether an entry with the identification type R/3 Customer Number (CRM002) exists for the business partner on the Identification tab page, and whether a supply chain unit exists for this entry.

If EWM does not find a distinct assignment, it cannot accurately find the routes and issues a message to this effect. ●

You also determine the following for the supply chain unit master data: ○

On the Bus.Char. (business character) tab page, you assign the business character to the supply chain unit as a planning location [Extern].

○

You have created a ship-to party or an address for a ship-to party. If you do not use addresses in the delivery, you assign the business partner of the ship-to party in the supply chain unit master data of the supply chain unit. If you want to create a ship-to party or an address for a ship-to party, in the SAP Easy Access screen choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order or Maintain Outbound Delivery. Specify the ship-to party as the partner role on the Partner tab page or use the Ordering Address pushbutton to specify the ship-to party’s address.

○

You specify the geocoordinates and the country key for the supply chain unit of the source location and the ship-to location in the supply chain master data on the General tab page.

SAP Extended Warehouse Management (SAP EWM)

510

206

SAP Online Help

20.07.2007

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

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

Features If either you or the system change one of the following fields in the delivery header or a delivery item in the delivery, EWM automatically executes new route determination: Delivery Header ●

Changing the route or setting the determination indicator for the route to Initial or Value Determined by System.

●

Changing the means of transport or setting the determination indicator for the means of transport to Initial or Value Determined by System.

●

Change to Delivery Date

●

Changing the final delivery date/time.

●

Changing the warehouse (of the source location).

●

Changing the ship-to party.

●

Changing the final ship-to party.

●

Changing the freight forwarder.

Delivery item

Delivery processing only executes new route determination for those items that are relevant for the route. This means that delivery processing does not execute new route determination for changes to text items, kit items, or items that are not warehouse-relevant. In addition, delivery processing only executes route determination or new route determination for those items that are not yet assigned to an outbound delivery order. ●

Changing the product.

●

Changing the delivery quantity.

●

Changing the shipping conditions.

●

Changing the weight or volume.

●

Changing the planned goods issue date/time.

●

Creating a new delivery item.

SAP Extended Warehouse Management (SAP EWM)

510

207

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

208

SAP Online Help

20.07.2007

Data Use in Route Determination Route determination uses various data from the delivery, a change in which also triggers new route determination. ●

From the delivery header, route determination uses the supply chain units of the warehouse and the ship-to party, for example.

●

Route determination uses certain delivery-relevant items (see Executing Automatic Route Determination [Seite 207]). Non delivery-relevant items are text or kit items, or items that are not warehouserelevant.

●

Route determination uses the latest planned goods issue date/time of all the relevant items of the delivery as the start date/time for the forward scheduling of route determination. The planned delivery date is used for backward scheduling.

●

If you manually specify the carrier, the route or the means of transport, or if an external system specifies them, route determination uses them as additional constraints. For example, you manually specify the carrier. Route determination determines routes for this carrier only as valid. Using the determination indicator [Extern], route determination identifies whether it automatically determined the field or whether you or an external system specified the field.

When route determination determines a valid route, it copies the following data to the delivery: ●

Route at header level

●

Means of transport at header level

●

Carrier at header level on the Partner tab page (if route determination automatically determined the carrier)

●

Date/time Departure from Yard at header level

●

Delivery date/time at header level

●

Sequence number at header level

●

Export relevance at header level

SAP Extended Warehouse Management (SAP EWM)

510

209

SAP Online Help

20.07.2007

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

Features Outbound Delivery Request With route determination in the outbound delivery request, Extended Warehouse Management (EWM) can execute a delivery split in different outbound delivery orders. If you have activated route determination in Customizing, EWM attempts to determine a common route for all delivery items. ●

If route determination determines a common route, the system does not execute a delivery split.

●

If route determination cannot determine a common route, EWM reexecutes route determination. This time, route determination determines one route for every routerelevant delivery item (see Execution of Automatic Route Determination [Seite 207]). If route determination determines varying routes for the delivery items, delivery processing creates an outbound delivery order for each route. In this way, you can, for example, transport heavy and also smaller products in two outbound delivery orders via separate routes within the same outbound delivery request. However, EWM always processes logically corresponding delivery items together (for example, because of Delivery Groups [Extern]).

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

210

SAP Online Help

20.07.2007

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

Features Redetermination of Routes You can execute route determination for one or more deliveries with the Redetermine pushbutton. For example, you can use an earlier or a later route. If you change your route master data, you can also execute route determination with the new master data using this function. ●

With the Departure Date/Time, Lead Time, and Next Trip fields, you have the option of determining that route determination carries out forward scheduling from a start date/time that is different from the default start date/time. If you use the Departure Date/Time field, route determination attempts to find a route or trip [Extern] with this date and time. If you use the Lead Time field, route determination attempts to find a route or trip that occurs after the current Departure from Yard date/time plus the lead time. This is specified in hours. If you use the Next Trip field, route determination attempts to find a route or trip that occurs (in relation to route or trip) directly after the current Departure from Yard date/time.

Note that you can only ever use one of these fields. Delivery processing saves the information (for Extended Warehouse Management (EWM) to use a changed departure date/time) to the delivery in the planned goods issue date/time of the items. A route redetermination also uses this date/time. ●

You can use the Aggregation field to include the total weight of the selected deliveries in route determination. This means that route determination also determines routes that it does not automatically find, for example, because the weight of the individual deliveries is too low.

●

You can use the Set Route to Determined Automatically indicator if route determination is to address routes specified manually or routes specified by an external system in the same way as it addresses routes that it automatically determines. If delivery processing executes a route redetermination, route determination uses the route that was found automatically. If you set this indicator, route determination also sets the determination indicator [Extern] of the route to Determined Automatically.

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

SAP Extended Warehouse Management (SAP EWM)

510

211

SAP Online Help

20.07.2007

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

212

SAP Online Help

20.07.2007

Connection of Delivery Processing to Serial Numbers Use You can use serial numbers in the delivery so that you can document them for the delivery and flag them in goods receipt.

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

SAP Extended Warehouse Management (SAP EWM)

510

213

SAP Online Help

20.07.2007

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

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

SAP Extended Warehouse Management (SAP EWM)

510

214

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

215

SAP Online Help

20.07.2007

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

Prerequisites ●

You have defined reference document categories in Customizing for EWM under Cross-Process Settings → Delivery Processing → Reference Documents → Define Reference Document Categories.

●

You have assigned these reference document categories that correspond to the previous document types you use to a transit procedure and have set the TrsPrcRel (transit procedure relevance) indicator. You do this in Customizing for EWM under Interfaces → GTS Integration → Define Previous Document Types.

Process ...

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

If the customs authority allows the vehicle to be unloaded, SAP GTS sends a notification of the unloading permission to EWM. EWM sets the status type Transit Procedure of the inbound delivery to the status value Released and unlocks the inbound delivery for additional goods receipt process steps.

○

If the customs authority does not allow the vehicle to be unloaded because it is performing a customs inspection, unloading is delayed.

SAP Extended Warehouse Management (SAP EWM)

510

216

SAP Online Help

20.07.2007

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

217

SAP Online Help

20.07.2007

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

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

Process ...

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

If the customs authority allows the vehicle to be loaded, you set the status type Transit Procedure of the outbound delivery in EWM to the status value Released. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery and then the Transit Procedure pushbutton. In the dropdown menu, choose Set Status to “Release”. EWM releases the locked outbound delivery for additional goods issue process steps.

○

If the customs authority does not allow the vehicle to be loaded because it is performing a customs inspection, loading is delayed. You can set the status type Transit Procedure of the outbound delivery to the status value Customs Insp.. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery and then the Transit Procedure pushbutton. In the dropdown menu, choose Set Status to “Blocked for Customs”. After the customs inspection, you set the status type Transit Procedure of the outbound delivery in EWM to the status value Released. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery and then the Transit Procedure pushbutton. In the dropdown menu, choose Set Status to “Release”. EWM releases the outbound delivery for additional goods issue process steps.

SAP Extended Warehouse Management (SAP EWM)

510

218

SAP Online Help

20.07.2007

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

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

SAP Extended Warehouse Management (SAP EWM)

510

219

SAP Online Help

20.07.2007

Connection of Delivery Processing to Safekeeping Use You can use safekeeping [Seite 962] for inbound deliveries in delivery processing.

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

Prerequisites ●

You have performed Customizing for the transit procedure [Seite 216] in Extended Warehouse Management (EWM).

●

You have set the Customs Block indicator in Customizing for EWM under Extended Warehouse Management → Interfaces → GTS Integration → Define Previous Document Types. As a result, you have defined that the previous document type is relevant to customs blocked stock.

●

If you want to define a customs block for certain previous document types, you must define stock types with the role Customs Blocked Stock in Customizing for EWM under Extended Warehouse Management → Master Data → Product → Define Stock Types.

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

If you change the previous document number or previous document type again before posting goods receipt, EWM automatically changes the stock type.

•

If you have posted the first (partial) goods receipt or EWM has created a warehouse task (unloading warehouse task or putaway warehouse task), you cannot change the previous document number or previous document type in the delivery.

•

If a product is subject to a batch management requirement and is relevant to customs warehousing, you must specify a country of origin in the delivery for goods receipt posting.

SAP Extended Warehouse Management (SAP EWM)

510

220

SAP Online Help

20.07.2007

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

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

Features When the ERP system sends a posting change delivery for a scrapping to delivery processing, delivery processing automatically creates a posting change request for scrapping, or you do this manually. Delivery processing also checks whether the product in this posting change request is relevant to customs warehousing. ●

●

If the product is relevant to customs warehousing, delivery processing requests a scrapping reference number from SAP GTS. ○

If SAP GTS sends this number immediately, delivery processing continues to process the posting change request for scrapping.

○

If SAP GTS does not send this number immediately, delivery processing locks the posting change request to prevent further processing, for example, warehouse task creation. SAP GTS asks the customs authority for permission for the scrapping. As soon as SAP GTS gets this permission, it sends the scrapping reference number to delivery processing. Delivery processing unlocks the posting change request and continues with the processing.

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

See also: Performing Scrapping [Seite 130]

SAP Extended Warehouse Management (SAP EWM)

510

221

SAP Online Help

20.07.2007

Connection of Delivery Processing to Checks in SAP GTS Purpose Extended Warehouse Management (EWM) uses the compliance check and letter of credit check from SAP Global Trade Services (SAP GTS) to check whether an outbound delivery can be delivered to a certain goods recipient. The connection to SAP GTS means you can make use of the following checking criteria for your deliveries: ●

Checking criteria for the compliance check: ○

Sanctioned Party List [Extern]

○

Embargos, for example, no exports from the USA to Cuba

○

Legal control, meaning licenses For example, a product is only allowed to be exported in a certain quantity and to a certain goods recipient.

●

Letter of credit check: Check for whether letter of credit is still valid

The system performs the checks in the following cases: ●

When you or EWM generate an outbound delivery order.

●

If EWM changes certain fields in an outbound delivery order or outbound delivery, or you manually change certain fields (for example, address, partner, or delivery quantity) in an outbound delivery, EWM checks the outbound delivery order or the outbound delivery.

●

If you determined in Customizing that the outbound delivery is relevant for the legal control, EWM checks the outbound delivery before goods issue.

Prerequisites ●

●

In Customizing, you can define the item types for which EWM is to perform the checks: ○

Define a status profile for the checks, and do not set the Inactive indicator for the corresponding status type DGT GTS check. For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Delivery Processing → Status Management → Define Status Profile.

○

Assign this status profile to an item type. For more information, see the IMG for EWM under Goods Issue Process → Outbound Delivery → Define Position Types for Outbound Delivery Process Using Wizard .

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

●

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

SAP Extended Warehouse Management (SAP EWM)

510

222

SAP Online Help ●

20.07.2007

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

Process ...

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

If you are working with direct outbound delivery orders, no data from a preceding document is available in EWM. For this reason, EWM performs restricted checks only. EWM does not perform a letter of credit check or a check for licenses for direct outbound delivery orders. If you are working with kit to stock, EWM does not perform any checks in SAP GTS. 2. SAP GTS performs the checks and returns a status. ○

If SAP GTS checks for the outbound delivery order contain errors, SAP GTS returns the relevant status. EWM sets the status GTS Check/Technical Error or GTS Check/Check, NotOK, and does not create an outbound delivery for this outbound delivery order.

○

If SAP GTS checks for the outbound delivery contain errors, SAP GTS returns the relevant status. EWM sets the status GTS Check/Technical Error or GTS Check/Check, NotOK, and does not permit a goods issue posting for this outbound delivery.

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

SAP Extended Warehouse Management (SAP EWM)

510

223

SAP Online Help

20.07.2007

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

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

Process SAEWM ...

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

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

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

IT = Italy

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

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

SAP Extended Warehouse Management (SAP EWM)

510

224

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

225

SAP Online Help

20.07.2007

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

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

SAP Extended Warehouse Management (SAP EWM)

510

226

SAP Online Help

20.07.2007

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

Prerequisites ●

You have defined a schedule condition for the PPF action that contains the call of method /SCWM/CL_DLV_PPF_CONF=>EVALUATE. For more information, see the method documentation. For more information about the PPF, see the SAP Help Portal help.sap.com under SAP NetWeaver → SAP NetWeaver Library → SAP NetWeaver by Key Capability → Application Platform by Key Capability → Business Services → Business Communication Services → Generic Business Tools for Application Developers (BC-SRV-GBT) → Post Processing Framework (BC-SRVGBT).

●

You have made the following settings for the condition technique in Customizing for Extended Warehouse Management (EWM):

...

a. Create field catalog b. Create condition tables c. Create access sequences d. Create condition types e. Maintain determination procedure f. Assign determination procedure g. Create condition maintenance group h. Register condition maintenance group For more information, see the Implementation Guide (IMG) for EWM under CrossProcess Settings → Delivery Processing → Actions → Configure Action Scheduling.

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

SAP Extended Warehouse Management (SAP EWM)

510

227

SAP Online Help

20.07.2007

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

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

Activities ●

If you want to define the configuration of scheduling of PPF actions, perform the IMG activities in the sequence specified under Prerequisites in the Implementation Guide (IMG) for EWM under Cross-Process Settings → Delivery Processing → Actions → Configure Action Scheduling.

●

If you want to view or edit schedule conditions for PPF actions, in the IMG for EWM, choose Cross-Process Settings → Delivery Processing → Actions → Change Actions and Conditions → Define Conditions.

●

If you want to edit condition records for the schedule condition of a PPF action, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Actions → Maintain Condition Records for PPF Schedule Conditions.

●

If you want to view and edit PPF actions, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Actions → Process and Display PPF Actions.

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

SAP Extended Warehouse Management (SAP EWM)

510

228

SAP Online Help

20.07.2007

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

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

Procedure ...

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

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

Result You have created a new condition record.

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

SAP Extended Warehouse Management (SAP EWM)

510

229

SAP Online Help

20.07.2007

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

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

SAP Extended Warehouse Management (SAP EWM)

510

230

SAP Online Help

20.07.2007

Automatic Generation of a VAS Order for the Warehouse Request Item Purpose You can generate value-added service orders [Extern] (VAS orders) automatically in Extended Warehouse Management (EWM) to document and monitor these value-added services.

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

Process ...

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

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

SAP Extended Warehouse Management (SAP EWM)

510

231

SAP Online Help

20.07.2007

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

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

Process ...

Changing a VAS Order 1. You edit the VAS order and with that change the status of the VAS order [Seite 538]. 2. EWM automatically adjusts the VAS Order status of the warehouse request item: ○

If you set the status of the VAS order to In Process, EWM also changes the VAS Order status to In Process.

○

If you set the status of the VAS order to Completed or Completed with Quantity Variance, EWM sets the VAS Order status to Completed.

Deleting a VAS Order ...

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

SAP Extended Warehouse Management (SAP EWM)

510

232

SAP Online Help

20.07.2007

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

Prerequisites ●

A VAS order exists for the warehouse request item.

●

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

Process Changing the Warehouse Request ...

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

233

SAP Online Help

20.07.2007

Kit in the Warehouse Request for the Outbound Delivery Order Definition Describes a piece list that you always deliver in a complete and assembled form.

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

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

Structure The outbound delivery contains the following items as kit information, corresponding to the levels of a kit: ●

Kit Header Item [Extern]

●

Kit Component Item [Extern] The kit header item is a direct predecessor of this item.

●

Replaced kit component item [Extern] The kit header item is a direct predecessor of this item, and the kit component item is in turn a subitem of this item.

SAP delivers preconfigured item types as standard for these kit items. You can use these to individually control the kit items in an outbound delivery.

If you want to change the settings of the preconfigured item types, you must note the following regarding the profiles. We recommend that you use the standard profiles shipped by SAP. ●

You must make sure that the status profile for the item type of the kit header and of the replaced kit components prevents them from being considered in warehouse processing. For example, you must therefore deactivate the picking relevance and the goods movement relevance.

●

You must configure the quantity offsetting profile of the kit header and of the replaced kit components so that EWM does not calculate any open quantities for picking or goods issue, for example. This means that you must set the corresponding quantity roles in this quantity offsetting profile to inactive.

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

SAP Extended Warehouse Management (SAP EWM)

510

234

SAP Online Help

20.07.2007

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

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

Integration ●

Integration with the ERP system EWM receives information about the kit as part of the outbound delivery from the ERP system. The ERP system also saves the kit as items in the outbound delivery (see also Kit to Order [Seite 349]).

●

Integration with value-added service orders (VAS orders) You can create a VAS order for the kit header item. EWM copies the kit component items into the VAS order as items (see also VAS Order for the Kit Header Item of the Warehouse Request [Seite 356]).

●

Integration with warehouse processing Warehouse processing in EWM handles kit component items in the same way as outbound delivery items, in other words, you can pick, pack, and load them.

SAP Extended Warehouse Management (SAP EWM)

510

235

SAP Online Help

20.07.2007

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

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

Prerequisites ●

An outbound delivery with kit header items and kit component items exists.

●

The quantity of the kit header item is greater than one.

●

All kit component items are completely picked.

●

If the system is to automatically generate an HU item for the kit header in the pickhandling unit (pick-HU), set the Create Kit Header Item indicator in Customizing. For more information about the packing profile, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Outbound Delivery → Define EWM-Specific Settings for Item Types.

Process Item Split for Unpacked Kits ...

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

Item Split for Packed Kits ...

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

SAP Extended Warehouse Management (SAP EWM)

510

236

SAP Online Help

20.07.2007

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

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

SAP Extended Warehouse Management (SAP EWM)

510

237

SAP Online Help

20.07.2007

Delivery Quantity Correlation for Kits Use If you or the system make changes to the delivery quantity, Extended Warehouse Management (EWM) recalculates the delivery quantity changes for the following items: ●

Kit header items

●

Kit component items

●

Batch subitems

●

Subitems occurring through substitution

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

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

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

Features ●

When EWM performs a split, or when you manually change a delivery quantity for a kit header item, EWM recalculates the delivery quantities of all delivery items belonging to the kit. EWM calculates the delivery quantities for new and changed kit header items and kit component items.

●

When EWM performs a pick denial, or when you manually change a delivery quantity for a kit component item, EWM recalculates the delivery quantities from bottom to top through the hierarchy levels.

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

SAP Extended Warehouse Management (SAP EWM)

510

238

SAP Online Help ●

20.07.2007

EWM considers the process code in the delivery quantity correlation.

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

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

Delivery Quantity Recalculation for the Batch Split When you perform a charge split manually on the user interface prior to picking, or when EWM performs a batch split automatically, EWM performs a corresponding delivery quantity correlation. Here, EWM ensures that the total of the batch subitem delivery quantities is not greater than the delivery quantity of the split kit component item. ●

If the total is the same in the batch split, the delivery quantity is not changed.

●

If the total is less in the batch split, the delivery quantity is again not changed. However, EWM does not distribute the delivery quantity across all batch subitems. This enables you or the system to add additional batch subitems at a later time.

●

If the total is greater in the batch split, the delivery quantity of the batch subitems is changed corresponding to the delivery quantity.

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

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

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

SAP Extended Warehouse Management (SAP EWM)

510

239

SAP Online Help ●

20.07.2007

Directly changing the delivery quantity field on the user interface: ○

On the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery and then choose the Quantity column on the Items tab page. Change the delivery quantity.

○

On the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order and then choose the Quantity column on the Items tab page. Change the delivery quantity.

○

On the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery and then choose the Quantity column on the Items tab page. Change the delivery quantity.

●

Changing the delivery quantity in the pick denial [Seite 327]

●

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

●

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

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

SAP Extended Warehouse Management (SAP EWM)

510

240

SAP Online Help

20.07.2007

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

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

Batch subitem 67 for batch 4: reduce to 3 pieces

SAP Extended Warehouse Management (SAP EWM)

510

241

SAP Online Help

20.07.2007

■

Batch subitem 65 for batch 3: no change, remains at 2 pieces

■

Kit component item 60: reduce to 5 pieces

■

Kit component item 50: no change, remains at 5 pieces

■

Kit component item 40: reduce to 10 pieces

■

Kit component item 30: reduce to 10 pieces, although you only reduced the delivery quantity by 8 pieces. However, since a fixed ratio of 1:10 is defined, EWM reduces the delivery quantity of this item by 10 pieces.

■

Kit header item 10: reduce to 1 piece

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

SAP Extended Warehouse Management (SAP EWM)

510

242

SAP Online Help

20.07.2007

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

Integration See Creation of Inspection Document [Seite 869]

Prerequisites ●

You have carried out the Customizing for creating inspection documents [Seite 869].

●

You have defined inspection rules (see Master Data [Seite 855]).

●

In the delivery, you have specified all the data necessary for the creation of an inspection document. If not all of the necessary data exists in the delivery by the time at which EWM is to create the inspection documents, EWM creates the inspection documents later. For example, EWM is to create an inspection document when the inbound delivery is activated. The batch number is required for creation. EWM only creates the inspection document once you have specified the batch number.

Features In the following cases, EWM creates inspection documents in the background, regardless of Customizing: ●

If you or EWM activate an inbound delivery

●

If EWM sets the status In Yard for an inbound delivery

●

Before EWM creates a warehouse task

●

Before you post the goods receipt

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

SAP Extended Warehouse Management (SAP EWM)

510

243

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

244

SAP Online Help

20.07.2007

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

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

Features A batch number can be specified via a system (an ERP system, for example) or you specify it directly in EWM. Using a determination indicator, EWM determines where the batch information originates from and whether you can still change the batch number. The following options exist: ●

A different system specifies a batch number, for example in a purchase order in the ERP system. You must use this batch number, that is, you cannot change the batch number.

●

A different system proposes a batch. For example, you have entered the batch in the inbound delivery of the ERP system. You can change this batch.

●

You specify a known batch number directly in EWM, that is, it does not originate from another system. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery Order. Go to the form view and enter a batch number in the Batch field. EWM can also create new batch numbers for inbound deliveries. For this, leave Batch. As soon as you save the the Batch field empty and choose the function inbound delivery, EWM creates a new batch number. You can also directly specify the existing batch number for outbound deliveries. To do so, on the SAP Easy Access screen, choose Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order. Go to the form view and specify the batch number. You can only change the batch number before saving. You can also specify the batch in the corresponding warehouse task. EWM copies the batch to the delivery. Here, EWM creates a batch subitem with the confirmed quantity and batch.

When you are processing the inbound or outbound delivery, EWM copies the batch characteristics to the delivery, for example, the country of origin, minimum shelf life, or the expiry date. You can split a batch in the inbound delivery. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery Order. Select a batch and choose the function Batch Subitem. EWM creates a corresponding subitem for the batch.

SAP Extended Warehouse Management (SAP EWM)

510

245

SAP Online Help

20.07.2007

Integration of Delivery Processing with Pickup Use Delivery processing supports goods issue for the pickup [Extern]. Goods issue for the pickup can be planned or unplanned.

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

Prerequisites ●

You have defined the account assignment categories in Customizing for EWM. For more information, see the Implementation Guide (IMG) for EWM under Goods Issue Process → Outbound Delivery → Define Account Assignment Category and Allow in Warehouse Number.

●

You have defined a process profile for the pickup in Customizing for EWM. For more information, see the IMG for EWM under Cross-Process Settings → Delivery Processing → Process Management and Control.

●

You have defined a status profile for the pickup in Customizing for EWM. For more information, see the IMG for EWM under Cross-Process Settings → Delivery Processing → Status Management → Define Status Profiles.

●

You have assigned the process profile for the pickup to a document type in Customizing for EWM. For more information, see the IMG for EWM under Goods Issue Process → Outbound Delivery → Manual Settings → Define Document Types for Outbound Delivery Process.

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

Features ●

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

●

Planned pickup

SAP Extended Warehouse Management (SAP EWM)

510

246

SAP Online Help

20.07.2007

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

Activities ●

If you want to generate or edit direct outbound delivery orders for the pickup, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery -> /SCWM/SGI – Pickup.

●

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

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

Direct Outbound Delivery Order [Seite 167]

SAP Extended Warehouse Management (SAP EWM)

510

247

SAP Online Help

20.07.2007

Communication from EWM to the ERP System Use Communication from Extended Warehouse Management (EWM) to the ERP system uses defined interfaces and enables distribution, changes to, and confirmation of delivery-relevant data. In the ERP system, the interfaces between EWM and the ERP system itself are based on deliveries. In EWM, they are based on the following: ●

Inbound delivery notifications and inbound deliveries in the inbound delivery process

●

Outbound delivery orders and outbound deliveries in the outbound delivery process

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

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

ERP System Delivery 1

Completed delivery 1

Changed delivery

Delivery

2

Confirmation (goods movement)

Copy

1

Split message

Change message

Delivery 2

3

Executed delivery 1

4

Completed executed delivery 1

Changed warehouse request

Warehouse request Delivery change

Delivery

Executed delivery 2

split

SAP SCM, EWM ...

1. Distribution of deliveries

SAP Extended Warehouse Management (SAP EWM)

510

248

SAP Online Help

20.07.2007

○

Send from ERP system to EWM

○

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

2. Changes to deliveries ○

Send from EWM to the ERP system (for example, confirmation of a pick denial from EWM to the ERP system)

○

Send from the ERP system to EWM (for example, changed ASN from vendor)

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

Prerequisites ●

You are using an ERP system. Here, you define for each plant and storage location whether you manage your warehouse in a separate, decentralized EWM. EWM receives the requests for goods movements from the ERP system.

●

Transmit all information to EWM that EWM requires for the goods movements. These include:

●

○

Partner master data (for example, customers, vendors, transportation service providers)

○

Location master data (for example, customers, vendors, plants)

○

Product master data

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

Features The following functions are available for EWM and the ERP system for the purpose of processing inbound and outbound deliveries. ●

●

Processing of Inbound Deliveries [Seite 251] ○

Receipt of an inbound delivery from the ERP system to EWM

○

Receipt of a change request for inbound deliveries from the ERP system to EWM

○

Notification of changed data before goods receipt from EWM to the ERP system

○

Confirmation of a goods receipt from EWM to the ERP system

○

Notification of a reversal or correction of the goods receipt from EWM to the ERP system

○

Notification of an inbound delivery split from EWM to the ERP system

Processing of Outbound Deliveries [Seite 253] ○

Receipt of an unchecked outbound delivery from the ERP system to EWM

○

Receipt of a checked outbound delivery from the ERP system to EWM

○

Notification of an outbound delivery change from EWM to the ERP system

SAP Extended Warehouse Management (SAP EWM)

510

249

SAP Online Help

20.07.2007

○

Quantity change request from EWM to the ERP system

○

Confirmation of a goods issue from EWM to the ERP system

○

Notification of a reversal of the goods issue from EWM to the ERP system

○

Direct billing or invoicing before goods issue

○

Communication of an outbound delivery split from EWM to the ERP system

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

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

SAP Extended Warehouse Management (SAP EWM)

510

250

SAP Online Help

20.07.2007

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

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

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

Features ●

Receipt of an inbound delivery from the ERP system in EWM EWM receives an inbound delivery notification as a result of the following process: The ERP system receives an advanced shipping notification (ASN) and validates this. The ERP system creates an inbound delivery and sends an inbound delivery notification to EWM. EWM can also receive an inbound delivery notification as a result of inbound deliveries created in the ERP system. EWM uses the inbound delivery notification to create an inbound delivery. If errors occur during ASN validation in the ERP system, the ERP system gives the incorrect delivery items an error status before sending the information to EWM. EWM blocks the incorrect delivery items for execution. Delivery items that do not contain errors are open for execution even if the inbound delivery contains other incorrect delivery items. The following rules apply when solving the errors: ○

You can remove the errors in the ERP system. The ERP system sends a change message to EWM. EWM processes this change message as long as the inbound delivery is not yet in processing in EWM.

○

You can remove the errors in EWM. EWM sends the changed data with the goods receipt confirmation to the ERP system. The ERP system decides whether it accepts the data to correct the errors, or whether you need to manually process the inbound delivery again in the ERP system before the system processes the goods receipt confirmation. In this case, the ERP system returns the message, which was originally sent by EWM, to the qRFC inbound queue. After you have solved the error in the ERP system manually, you can start the message again in the qRFC inbound queue in the ERP system. The ERP system then continues processing accordingly.

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

Receipt of a change request for inbound deliveries from the ERP system in EWM

SAP Extended Warehouse Management (SAP EWM)

510

251

SAP Online Help

20.07.2007

The vendor can send a new ASN or an ASN rejection for an existing inbound delivery. The ERP system receives these messages and validates them. It forwards them to EWM. EWM checks whether it can replace the existing inbound delivery. If it can replace the inbound delivery, it sends a confirmation message to the ERP system. If EWM cannot replace the existing inbound delivery, it sends a rejection message to the ERP system. If the inbound delivery is not yet being processed, in other words, if the status Warehouse Activity does not have the value Not Started, EWM replaces the inbound delivery. ●

Notification of changed data before goods receipt from EWM to the ERP system If you make changes (such as setting the transit status In Yard or entering new items) in EWM, EWM sends these to the ERP system before confirming the goods receipt. If you only change the transit status in EWM, EWM only sends the header data for the inbound delivery to the ERP system. The ERP system replaces the header data accordingly. If you also replace relevant item data in EWM, EWM sends the entire document and the ERP system replaces the entire document with the data from EWM. The ERP system does not overwrite any data that cannot be provided by EWM (for example, the document type or company code).

●

Confirmation of a goods receipt from EWM to the ERP system For inbound deliveries, you can make either partial (partial goods receipt) or complete goods receipt posting. You can specify whether there should be a confirmation to the ERP system for each individual partial goods receipt, or for the entire delivery. You can also specify whether EWM should also transfer the current HU data with the goods receipt confirmation to the ERP system.

●

Notification of a reversal or correction of the goods receipt from EWM to the ERP system This enables you to correct or reverse goods movement postings. EWM creates a material document for these postings, which triggers confirmation of the correction or cancellation to the ERP system.

●

Notification of an inbound delivery split from EWM to the ERP system You can split inbound deliveries in EWM. EWM creates new inbound deliveries for this delivery split, and reports them to the ERP system. EWM determines the document number and item number in the ERP system. You must have defined the number range intervals in Customizing. These number ranges must not overlap with the number ranges in the ERP system.

For more information about the interfaces that enable these functions, see Interfaces for Communication from EWM to the ERP System [Seite 257]. For more information, see Inbound Delivery [Seite 88] and Creation of a Warehouse Request for an Inbound Delivery [Seite 113].

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

SAP Extended Warehouse Management (SAP EWM)

510

252

SAP Online Help

20.07.2007

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

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

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

Features ●

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

An outbound delivery request

○

An outbound delivery order

In EWM, you cannot create an outbound delivery for an outbound delivery order that EWM has created from an unchecked delivery in the ERP system. ●

Receipt of a checked outbound delivery from the ERP system If the ERP system converts unchecked outbound deliveries into checked outbound deliveries, then it sends two messages to EWM. ○

A deletion message for deleting an outbound delivery request, and an outbound delivery order that EWM created for the unchecked outbound delivery.

○

A message for creating an outbound delivery request and an outbound delivery order for the checked outbound delivery

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

An outbound delivery request

○

An outbound delivery order

In EWM, you can create an outbound delivery for an outbound delivery order that EWM has created from a checked delivery of the ERP system. ●

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

SAP Extended Warehouse Management (SAP EWM)

510

253

SAP Online Help

20.07.2007

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

Quantity change requests from the ERP system EWM can execute quantity change requests for the following: ○

For checked deliveries, based on sales order changes in SAP CRM.

○

For checked deliveries, based on new assignments of order confirmations by SAP Advanced Planning & Optimization.

EWM accepts a quantity change as long as the outbound delivery order is not yet being processed. If EWM accepts the quantity change, it reports the execution of the quantity change to the ERP system. EWM rejects any quantity changes for outbound delivery orders that are already in processing. The Warehouse Activity status for the outbound delivery order in this case is Warehouse Act./Part. Completed. If EWM rejects the quantity change, it reports the rejection of the quantity change to the ERP system. ●

Communication of a goods issue confirmation to the ERP system EWM uses an outbound delivery to report a goods issue posting or reversal to the ERP system. You can only cancel an outbound delivery if it does not have the status In Transit.

●

Direct billing or invoicing before goods issue You can print the invoice in the warehouse, if necessary, even before the goods issue. EWM uses an outbound delivery order to create an outbound delivery before the goods issue posting. If you have defined the status Invoicing Before Goods Issue for a route in Customizing, then EWM sets an indicator for this status that results in direct billing. If an outbound delivery order has this indicator, EWM creates the outbound delivery automatically. For automatic creation, EWM must also have set the Loading status to Started. After automatic creation of the outbound delivery, EWM triggers confirmation of the data to the ERP system for the purpose of direct billing. The ERP system forwards this data to the invoicing system in SAP CRM.

●

Communication of an outbound delivery split to the ERP system EWM can split outbound delivery order, for example, if the requested quantity does not fit onto the means of transport. New outbound deliveries are generated by this split, which EWM reports to the ERP system. EWM determines the document number and item number in the ERP system. You must have defined the number range intervals in Customizing. These number ranges must not overlap with the number ranges in the ERP system.

SAP Extended Warehouse Management (SAP EWM)

510

254

SAP Online Help

20.07.2007

For more information about Customizing for number range intervals, see the Implementation Guide (IMG) for EWM under Interfaces → ERP Integration → Delivery Processing → Define Number Ranges for ERP Documents. ●

Replication of outbound delivery orders that were created manually in EWM, to ERP system If you create and save a direct outbound delivery order [Seite 167] manually in EWM without errors, EWM sends this to the ERP system immediately after saving, using an interface for communicating between EWM and ERP.

For more information about the interfaces that enable these functions, see Interfaces for Communication from EWM to the ERP System [Seite 257]. See also: ●

Outbound Delivery Request [Seite 90]

●

Outbound Delivery Order [Seite 91]

●

Outbound Delivery [Seite 93]

●

Creation of a Warehouse Request for an Outbound Delivery Order [Seite 116].

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

SAP Extended Warehouse Management (SAP EWM)

510

255

SAP Online Help

20.07.2007

Delivery Processing Administration Use The following provides you with technical information for: ●

Interfaces for Communication from EWM to the ERP System [Seite 257]

●

Functional Enhancement Through Business Add-Ins (BAdIs) [Seite 260]

●

Data Enhancement for Warehouse Requests [Seite 261]

SAP Extended Warehouse Management (SAP EWM)

510

256

SAP Online Help

20.07.2007

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

Features Interfaces for Inbound Deliveries Interface Name

Description

Additional Information

/SPE/INB_DELIVERY_SAVEREPLICA

Replication of inbound deliveries EWM to the ERP system (EWM → ERP System)

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

/SCWM/INB_DLV_SAVEREPLICA

Replication of manually created inbound deliveries in the ERP system to EWM (ERP system → EWM)

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

/SPE/INB_DELIVERY_CONFIRM_DECENTRAL

Confirmation of the goods receipt in EWM (EWM → ERP system)

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

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)

SAP Extended Warehouse Management (SAP EWM)

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

510

257

SAP Online Help

20.07.2007

Confirmation of deletion of an inbound delivery (EWM → ERP system) /SCWM/INB_DELIVERY_REPLACE

Replication of changed inbound deliveries (ERP system → EWM)

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

/SPE/INB_DELIVERY_SPLIT

Reporting of inbound deliveries that were generated by the split in EWM (EWM → ERP system)

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

/SPE/INB_DELIVERY_RESPONSE

Reject or confirm replicated inbound delivery changes (EWM → ERP system)

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

Interfaces for Outbound Deliveries Interface Name

Description

Additional Information

/SCWM/OUTB_DLV_SAVERE PLICA

Replication of unchecked and checked deliveries from ERP system to EWM (ERP system → EWM)

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

BAPI_OUTB_DELIVERY_CO NFIRM_DECENTRAL

Confirmation of unchecked and checked deliveries for follow-on functions (for example, goods issue, invoicing before goods issue) (EWM → ERP system)

For more information, see the function module description for BAPI_OUTB_DELIVERY_CO NFIRM_DECENTRAL.

BAPI_OUTB_DELIVERY_CH ANGE

Confirmation (at delivery item level) of quantity change request for checked deliveries (EWM → ERP system)

For more information, see the function module description for BAPI_OUTB_DELIVERY_CH ANGE.

Change checked deliveries (EWM → ERP system) Confirm pick denials (EWM →

SAP Extended Warehouse Management (SAP EWM)

510

258

SAP Online Help

20.07.2007 ERP system) Reversal of goods issue (EWM → ERP system)

/SCWM/OUTB_DLV_CHANG E

Delete unchecked deliveries (ERP system → EWM)

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

BAPI_OUTB_DELIVERY_SPL IT_DECENTRAL

Confirm outbound delivery split to ERP system (EWM → ERP system)

For more information, see the function module description for BAPI_OUTB_DELIVERY_SPL IT_DECENTRAL.

/SCWM/OBDL_CHNG_QUAN _MUL

Quantity change requests for checked deliveries from ERP system to EWM (ERP system → EWM)

For more information, see the function module /SCWM/OBDL_CHNG_QUAN _MUL.

BAPI_OUTB_DELIVERY_REJ ECT

Reject a quantity change request (EWM → ERP system)

For more information, see the function module description for BAPI_OUTB_DELIVERY_REJ ECT.

/SPE/OUTB_DELIVERY_SAV EREPLICA

Replication of outbound delivery orders created manually in EWM, to ERP system (EWM → ERP system)

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

Activities If you want to call up the function module documentation or edit an interface, on the SAP Easy Access screen, choose Tools → ABAP Workbench → Development → Function Builder.

SAP Extended Warehouse Management (SAP EWM)

510

259

SAP Online Help

20.07.2007

Functional Enhancement Through Business AddIns (BAdIs) Use You use Business Add-Ins [Extern] (BAdIs) in delivery processing to execute user-defined functional enhancements in Extended Warehouse Management (EWM). You can carry out functional enhancements for the following areas: ●

Goods receipt process

●

Goods issue process

●

Warehouse-internal processes

●

Cross-process settings

●

Interfaces

Features For a description of the individual BAdIs, see the relevant BAdI documentation in the Implementation Guide (IMG) for EWM.

Activities ●

To call the BAdI documentation, see the Implementation Guide (IMG) for EWM under Business Add-Ins (BAdIs) for Extended Warehouse Management. Select the desired BAdI and choose

Documentation for IMG Activity.

EWM shows you the BAdI description of the IMG. ●

To carry out functional enhancements for delivery processing, see the Implementation Guide (IMG) for EWM under Business Add-Ins (BAdIs) for Extended Warehouse Management and then choose the area for which you want to carry out the functional enhancement. For more information about Business Add-Ins (BAdIs), see the SAP Library under SAP NetWeaver → Application Platform (SAP Web Application Server) → ABAP Technology → ABAP Workbench (BC-DWB) → ABAP Workbench: Tools → Further Concepts → Business Add-Ins.

SAP Extended Warehouse Management (SAP EWM)

510

260

SAP Online Help

20.07.2007

Data Enhancement for Warehouse Requests Use You can use the data enhancement in Extended Warehouse Management (EWM) to add your own fields to the warehouse request, and therefore to adapt it to your requirements.

Integration EWM uses the append technique for the data enhancement. You can use this method to add further structures to tables and structures. For more information, see Append Structure [Extern].

Features For the document categories for the warehouse request, EWM offers extendable structures for the document header and document item. You can extend these structures using append structures. Document categories for the warehouse request and corresponding structures Document Category

Structure for Document Header

Structure for Document Item

Inbound Delivery Notification

/SCDL/INCL_EEW_DR_HEAD_STR

/SCDL/INCL_EEW_DR_ITEM_STR

Inbound Delivery

/SCDL/INCL_EEW_DLV_HEAD_STR

/SCDL/INCL_EEW_DLV_ITEM_STR

Outbound Delivery Request

/SCDL/INCL_EEW_DR_HEAD_STR

/SCDL/INCL_EEW_DR_ITEM_STR

Outbound Delivery Order

/SCDL/INCL_EEW_DLV_HEAD_STR

/SCDL/INCL_EEW_DLV_ITEM_STR

Outbound Delivery

/SCDL/INCL_EEW_DLV_HEAD_STR

/SCDL/INCL_EEW_DLV_ITEM_STR

Stock Transfer

/SCDL/INCL_EEW_DLV_HEAD_STR

/SCDL/INCL_EEW_DLV_ITEM_STR

Posting Change Request

/SCDL/INCL_EEW_DR_HEAD_STR

/SCDL/INCL_EEW_DR_ITEM_STR

Posting Change

/SCDL/INCL_EEW_DLV_HEAD_STR

/SCDL/INCL_EEW_DLV_ITEM_STR

Several document categories have the same structure. This means that an enhancement is simultaneously present in more than one document category. EWM offers a range of Business Add-Ins (BAdIs) that you can use to fill the new fields with data.

Activities 1. On the SAP Easy Access screen, choose Tools → ABAP Workbench → Development → Dictionary. The ABAP Dictionary: Initial Screen screen appears. 2. Choose Data Type. 3. In the Data Type field, enter the structure that you want to enhance using an append structure. 4. Choose Change. 5. Create an append structure and enhance the append structure by adding your own fields. For more information, see Extending Tables and Structures [Extern]. 6. Enter data into the new fields. To do this, in Customizing for Extended Warehouse Management under Business Add-Ins (BAdIs) for Extended Warehouse Management enter the relevant BAdIs.

For the data enhancement for messages to the decentralized ERP system, choose the following BAdI: Extended Warehouse Management → Business Add-Ins (BAdIs) for Extended Warehouse Management → Interfaces → ERP Integration → Inbound Messages from ERP System to EWM → BAdI: Creation of Inbound Deliveries in EWM.

SAP Extended Warehouse Management (SAP EWM)

510

261

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

262

SAP Online Help

20.07.2007

Goods Receipt Purpose Putaway enables you to display your complex putaway process steps and includes the following functions: ●

Unloading [Seite 608]

●

Counting [Seite 295]

●

Deconsolidation [Seite 298]

●

Final Putaway [Seite 300]

It takes into account your warehouse arrangement (for example, putaway using identification points [Seite 408] in a high rack storage area) as well as the process-oriented rules and process flows defined by you (for example, counting requests, repacking). Extended Warehouse Management (EWM) contains putaway strategies [Seite 375] to simplify the search for appropriate storage bins. You can put away your products directly or through storage control [Seite 334]. You can only execute complex putaway processes by using handling units.

Prerequisites ●

You have defined the following basic settings in Customizing for Extended Warehouse Management (EWM): Basic settings are, for example: IMG Activity

Path in Implementation Guide (IMG)

Storage types, storage area, storage bins

IMG for EWM under Master Data → Define Storage Type → Define Storage Section → Storage Bins

●

Activity Areas

IMG for EWM under Master Data → Activity Areas → Define Activity Areas

Activities

IMG for EWM under Master Data → Activity Areas → Activities → Define Activity Areas

if required, work centers [Extern], for example, for deconsolidation

For more information about defining putaway steps, see the IMG for EWM under Master Data → Work Center → Define Work Center.

Doors

IMG for EWM under Master Data → Warehouse Door → Define Warehouse Door

Staging areas

IMG for EWM under Goods Issue Process → Define Staging Areas

You have displayed your putaway steps in the system. For more information about defining putaway steps, see the IMG for EWM under Cross-Process Settings → Warehouse Task → Layout-Oriented Storage Control or Process-Oriented Storage Control.

SAP Extended Warehouse Management (SAP EWM)

510

263

SAP Online Help ●

20.07.2007

All required processes are fully integrated. The system updates, for example, the inbound delivery in the warehouse activities.

Process ...

1. The process begins when SAP R/3 receives an advanced shipping notification from an external system (for example, SAP CRM) for a planned inbound delivery. 2. The ERP system uses this advanced shipping notification to create an inbound delivery, and distributes it to EWM. 3. EWM uses the data from this inbound delivery to create a warehouse request. This warehouse request is the starting point for the putaway process. If you reject the inbound delivery in EWM, EWM sets the planned delivery quantity to zero and notifies the ERP system. EWM ends the inbound delivery and sets the status of the warehouse request to Completed.

For more information, see Warehouse Request for Returns [Seite 132].

Result EWM uses the warehouse request to create one or more warehouse tasks for the putaway (putaway WT). You can use it to put away the products.

SAP Extended Warehouse Management (SAP EWM)

510

264

SAP Online Help

20.07.2007

Storage Control Use You can use the process-oriented as well as layout-oriented methods for storage control. The goal of storage control is to display your complex putaway or stock removal process steps based on your processes or your layout data. During putaway or stock removal, an individual process step can be executed on single level basis or on multi level basis (that is, through intermediate storage types). You can combine the process-oriented storage control with the layout-oriented storage control. Here, EWM always executes the process-oriented storage control first. The layoutoriented storage control then checks whether the sequence of putaway process steps is possible in layout view, and if required, adjusts the flow of the putaway or stock removal.

Based on the process-oriented storage control, EWM determined the following putaway process flow: ●

Unloading at door

●

Counting at counting station

●

Checking the quality

●

Executing value-added services

●

Putaway in high rack storage area

The layout-oriented storage control determines that a direct putaway in the high rack storage area is not possible and that the putaway must occur with the use of an identification point. ●

Unloading at door

●

Counting at counting station

●

Identification of goods at the ID point [Extern]

●

Putaway in high rack storage area

Integration Extended Warehouse Managment (EWM) uses the delivery to determine, via delivery type and delivery item among others, the warehouse process type. This contains the procedure, in other words, the putaway or stock removal process with different activities. EWM transfers this operation to the handling unit to be put away or removed from stock. The handling unit thus contains the information concerning what process steps are required for the putaway or stock removal.

Prerequisites You have defined the following in Customizing for the putaway: ●

Paramaters that specify the work station determination for the next function (for example, counting) within the goods receipt process The following parameters are possible:

SAP Extended Warehouse Management (SAP EWM)

510

265

SAP Online Help

●

○

Source storage type

○

Destination activity area or destination storage type

○

Warehouse process type

○

Handling unit type

20.07.2007

Determination of the warehouse process type, using the delivery type and delivery item type, among others.

Features For information about the features of storage control, see Process-Oriented Storage Control [Seite 336] and Layout-Oriented Storage Control [Seite 340].

SAP Extended Warehouse Management (SAP EWM)

510

266

SAP Online Help

20.07.2007

Process-Oriented Storage Control Use You use this type of storage control to map complex putaways or stock removals. In doing so, you combine your storage process steps into one storage process. You can also trace the status of the individual process steps.

Process-oriented storage control only operates with handling units.

Integration For more information about integration, see Storage Control [Seite 334].

Prerequisites For more information about the prerequisites, see Storage Control [Seite 334].

Features You define the process steps for your complex storage process. A process step is, for example, unloading, counting, or deconsolidating [Seite 298]. Extended Warehouse Management (EWM) recognizes internal process steps predefined by SAP and external steps that you can define yourself. Your external process stesps can base themselves on internal ones. In addition, internal or external process steps can be simple, such as unloading, or combined, such as deconsolidating. For more information, see Direct and Combined Storage Control [Seite 268]. The process steps for the processes Counting and Deconsolidating predefined by SAP can be dynamic [Extern]. During goods receipt or goods issue, EWM copies the predefined process steps from the storage process type to the handling unit. EWM assigns these process steps to a handling unit as soon as it has created or changed them.

Activities For Customizing of process-oriented storage control, in the Implementation Guide (IMG) for EWM, choose Cross-Process Settings → Warehouse Task → Define Process-Oriented Storage Control.

SAP Extended Warehouse Management (SAP EWM)

510

267

SAP Online Help

20.07.2007

Direct and Combined Storage Control (Putaway) Use If you want to execute a direct putaway, you do not have to define anything in the processoriented storage control [Seite 336]. If you want to define complex putaway processes, you have to use a combined processoriented storage control. Extended Warehouse Management (EWM) uses this during creation of a warehouse task to determine the intermediate storage types (for example, deconsolidation station, counting station). For information about integration and the prerequisites, see Storage Control [Seite 334] .

Features Direct Storage Control at Putaway If EWM determines that you are to put away a handling unit (HU) directly, it creates a warehouse task for this HU that determines the way from the source storage type to the destination storage type. For more information about updating the status, see Updating the Inbound Delivery in the GR Process [Seite 271]. The following graphic shows you the relationship between direct putaway and creation of warehouse tasks. Goods Receiving Area

Source Storage Type 9010

Warehouse Task 1

Destination Storage Type 0010

Source Storage Type 9011

Warehouse Task 2

Destination Storage Type 0020

Combined Storage Control at Putaway If EWM determines that you are to put away a HU from stock using one or more intermediate storage types, it creates one warehouse task per route section for this HU. •

One warehouse task that describes the route from source storage type to intermediate storage type Irrespective of your settings in Customizing, EWM also creates a warehouse task per product contained in the HU. If, for example, an inbound delivery is packed and the HU

SAP Extended Warehouse Management (SAP EWM)

510

268

SAP Online Help

20.07.2007

has no profile for process-oriented storage control, EWM creates product warehouse tasks at putaway. •

Based on your settings in Customizing, one warehouse task from the intermediate storage type to the next intermediate storage type, or to the final destination storage type. You can carry out different activities at the intermediate storage types. For example, within a putaway process, at an intermediate storage type, you can distribute HUs containing different products to putaway HUs. In combined putaway, you can determine the final destination storage type either right at the beginning of your putaway process, or later. EWM manages the intermediate storage types in the same way as standard storage types. For example, you can break these down into storage sections and storage bins. For more information about updating the status, see Updating the Inbound Delivery in the GR Process [Seite 271]. The following graphic shows you the relationship between combined putaway and creation of warehouse tasks.

Goods Receiving Area

Source Storage Type 9010

Source Storage Type 9011

Intermediate Storage Type 8000

Warehouse Task 1.1

Warehouse Task 2.1

Intermediate Storage Type 8010

Warehouse Task 1.2

Destination Storage Type 0010

Intermediate Storage Type 8020

Warehouse Task 2.2

Intermediate Storage Type 8030

Warehouse Task 2.3

Destination Storage Type 0020

Example Direct Goods Receipt The following is a sample process flow of a direct goods receipt. ...

1. The truck comes to the loading ramp. 2. You open the truck.

SAP Extended Warehouse Management (SAP EWM)

510

269

SAP Online Help

20.07.2007

3. In EWM, you confirm the arrival of the truck. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Shipping and Receiving. 4. EWM creates a WT for this delivery that directly specifies the destination storage bin. 5. You unload the truck. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Shipping and Receiving → Unload. 6. You count the number of pieces of your products and confirm these in the WT. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Confirm Warehouse Task. 7. You execute the putaway. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Confirm Warehouse Task. Combined Goods Receipt The following is a sample process flow of a combined goods receipt. ...

1. The truck comes to the loading ramp. 2. You open the truck. 3. In EWM, you confirm the arrival and opening of the truck. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Shipping and Receiving. 4. EWM creates a WT for this delivery that directly specifies the destination storage bin. 5. You unload the truck. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Shipping and Receiving → Unload. 6. You count the number of pieces of your products and confirm these in the WT. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Confirm Warehouse Task. 7. EWM indicates that a deconsolidation of the products is necessary. 8. You store your products at the intermediate storage location and confirm this. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Confirm Warehouse Task. 9. You execute the deconsolidation at the intermediate location. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Deconsolidation in Goods Receipt. 10. You store your products at the destination storage bin. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Confirm Warehouse Task.

SAP Extended Warehouse Management (SAP EWM)

510

270

SAP Online Help

20.07.2007

Updating the Inbound Delivery in the GR Process Use Extended Warehouse Management (EWM) updates the inbound delivery corresponding to the goods receipt activities. For the goods receipt process (GR process), EWM maps the warehouse with the goods receipt and interior of the warehouse areas. This allows EWM to determine the point in time from when a putaway is planned, that is, from when a warehouse activity exceeds the limit for the interior of the warehouse. The following information belongs to the goods receipt area: ●

Transportation units (TUs)

●

Storage bins at warehouse doors

●

Staging area groups

All storage types that do not correspond to goods receipt belong to the interior of the warehouse area. For example: ●

Work centers

●

Identification points

●

Final storage types

EWM updates the statuses Unloading, Putaway Planning and Putaway in the inbound delivery, corresponding to this warehouse mapping.

Features Updating an Inbound Delivery with a Handling Unit Warehouse Task (HU WT) For Packed Stock The following graphic and description shows you the connection between process steps in GR and updating the inbound delivery with an HU WT for packed stock. Unloading

1

2

Putaway Planning

3

4

5

Putaway

6

TU / Door Staging Area Group

Goods Receipt

Deconsolidation Final Storage Type

Interior of Warehouse

You perform the GR activities for unloading and putaway. EWM updates the inbound delivery and sets the status in the inbound delivery. Für ... ...

●

The following applies for the status Unloading: ○

If you confirm an HU WT that is moving from a door or TU to a staging area group, EWM sets the status Unloading in the inbound delivery (see number 1 in the graphic).

SAP Extended Warehouse Management (SAP EWM)

510

271

SAP Online Help ○

●

●

20.07.2007

If you confirm an HU WT that is moving from a staging area group to a door or a TU, EWM resets the status Unloading in the inbound delivery (see number 2 in the graphic).

The following applies for the status Putaway Planning: ○

If you or the system generate an HU WT that is moving from goods receipt to the interior of the warehouse, EWM sets the status Putaway Planning in the inbound delivery (see number 3 in the graphic).

○

If you cancel an HU WT that is moving from goods receipt to the interior of the warehouse, EWM resets the status Putaway Planning in the inbound delivery (see number 4 in the graphic).

○

If you confirm an HU WT that is moving from the interior of the warehouse to goods receipt, EWM resets the status Putaway Planning in the inbound delivery (see number 5 in the graphic).

The following applies for the status Putaway: If you confirm an HU WT that contains the final storage type, EWM sets the status Putaway in the inbound delivery (see number 6 in the graphic).

Updating an Inbound Delivery with a Product Warehouse Task (Product WT) For Unpacked Stock You perform the GR activities for unloading and putaway. EWM updates the inbound delivery and sets the status in the inbound delivery. Für ... ...

●

The following applies for the status Unloading: If you confirm a product WT for unpacked stock that is located in a TU or storage bin at the door, EWM sets the status Unloading in the inbound delivery. A prerequisite for this is that the destination location in the product HU is not a TU, or that the destination storage type in the product WT is not a door.

●

The following applies for the status Putaway Planning: ○

If you or the system generate a product WT that is moving from the goods receipt bin to another storage bin, EWM sets the status Putaway Planning in the inbound delivery.

○

If you cancel a product WT because EWM originally set the status Putaway Planning in the inbound delivery, EWM resets the status Putaway Planning in the inbound delivery.

○

If you move a product back to its original goods receipt bin with a product WT, EWM resets the status Putaway Planning in the inbound delivery.

If you move a product from the goods receipt bin to an HU, and this HU is in the interior of the warehouse, EWM always sets the status Putaway Planning in the inbound delivery. EWM does not update the status Putaway Planning unless the HU is in the interior of the warehouse. ●

The following applies for the status Putaway: If you confirm a product WT that contains the final storage type, EWM sets the status Putaway in the inbound delivery.

Updating an Inbound Delivery with Storage Control The following graphic and description shows you the connection between process steps in GR and updating the inbound delivery with storage control [Seite 334].

SAP Extended Warehouse Management (SAP EWM)

510

272

SAP Online Help

20.07.2007

Unloading

1

2

Putaway Planning

3

4

5

Putaway

6

TU / Door Staging Area Group

Goods Receipt

Deconsolidation Final Storage Type

Interior of Warehouse

Handling Unit Warehouse Task Product Warehouse Task

You perform the GR activities for unloading and putaway. EWM updates the inbound delivery and sets the status in the inbound delivery. ...

●

●

●

The following applies for the status Unloading: ○

If you confirm an HU WT that is moving from a door or TU to a staging area group, EWM sets the status Unloading in the inbound delivery (see number 1 in the graphic).

○

If you confirm an HU WT that is moving from a staging area group to a door or a TU, EWM resets the status Unloading in the inbound delivery (see number 2 in the graphic).

The following applies for the status Putaway Planning: ○

If you or the system generate a product WT for putaway and an HU WT for unloading, EWM always sets the status Putaway Planning in the inbound delivery corresponding to the warehouse activities for the product WT. EWM uses the HU WT to update the status Unloading in the inbound delivery (see number 3 in the graphic).

○

If you or the system generate an HU WT into the interior of the warehouse and no product WT for putaway exists, EWM always sets the status Putaway Planning in the inbound delivery corresponding to the warehouse activities for the HU WT (see number 4 in the graphic).

The following applies for the status Putaway: If you confirm a product WT that contains the final storage type, EWM sets the status Putaway in the inbound delivery corresponding to the product WT. If you confirm an HU WT that contains the final storage type, EWM sets the status Putaway in the inbound delivery corresponding to the HU WT. This means that, depending on which WT you confirm first, EWM sets the status Putaway in the inbound delivery with this WT (see number 6 in the graphic).

Updating an Inbound Delivery and Outbound Delivery Order in CrossDocking EWM performs cross-docking [Seite 544] (CD). For the CD-relevant products, EWM generates one or more pick-warehouse tasks (pick-WTs) for CD and updates the inbound delivery and the outbound delivery order simultaneously. For the other products, EWM generates standard product WTs. ●

The following applies for the status Unloading:

SAP Extended Warehouse Management (SAP EWM)

510

273

SAP Online Help

20.07.2007

○

If you confirm an HU WT that is moving from a door or TU to a staging area group, EWM sets the status Unloading in the inbound delivery.

○

If you confirm an HU WT that is moving from a staging area group to a door or TU, EWM resets the status Unloading in the inbound delivery.

Für ... ...

●

●

The following applies for the status Putaway Planning in the inbound delivery and the status Picking Planning in the outbound delivery order in CD: ○

If EWM generates a pick-WT for CD, the system sets the status Putaway Planning in the inbound delivery and the status Picking Planning in the outbound delivery order.

○

If you cancel a pick-WT for CD, EWM resets both the status Putaway Planning in the inbound delivery and the status Picking Planning in the outbound delivery order.

The following applies for the status Putaway in the inbound delivery and the status Picking in the outbound delivery order in CD: If you confirm a pick-WT for CD, EWM sets the status Putaway in the inbound delivery and the status Picking in the outbound delivery order.

SAP Extended Warehouse Management (SAP EWM)

510

274

SAP Online Help

20.07.2007

Layout-Oriented Storage Control Use You can use the layout-oriented storage control if stock movements in your warehouse do not travel from a source storage bin to a destination location directly, rather travel via intermediate storage bin.

The layout-oriented storage control only operates with handling units. One exception is the process display with picking or identification points. You use layout-oriented storage control in the material flow system [Seite 820] to define conveyor segments.

Integration For more information about integration, see Storage Control [Seite 334].

Prerequisites For more information about the prerequisites, see Storage Control [Seite 334].

Features For layout-oriented storage control, you define external warehouse process steps for your warehouse, including identification points [Extern] and pick points [Extern].

For example, you have a high rack storage area. If you want to move a product pallet from storage bin A (goods receiving area) to storage bin B (high rack storage area), the system should execute a contour and weight check to ensure that the product pallet can be put away in the high rack storage area safely. For this activity, Extended Warehouse Management (EWM) splits the warehouse order into two: one from storage bin A to identification point I, and a second from identification point I to storage bin B. You can move your goods using a pick point during picking.

Activities For Customizing of layout-oriented storage control, in the Implementation Guide (IMG) for EWM, choose Cross-Process Settings → Warehouse Task → Layout-Oriented Storage Control.

SAP Extended Warehouse Management (SAP EWM)

510

275

SAP Online Help

20.07.2007

Storage Group Definition The storage group is a grouping of storage bins within a storage type [Extern] that is used to determine intermediate storage bins.

Use Extended Warehouse Management (EWM) uses the storage group in layout-oriented storage control [Seite 340] to determine the intermediate storage bins. The material flow system [Seite 820] also uses layout-oriented storage control and thereby the storage group to define conveyor segments.

Structure The storage group consists of a four-character identifier that you assign to a warehouse number and a storage type.

Integration EWM uses storage groups in layout-oriented storage control and in the material flow system.

Example You group all the storage bins in an aisle into a storage group since you want to take the goods that you remove from this aisle to an interim storage bin at the end of the aisle.

SAP Extended Warehouse Management (SAP EWM)

510

276

SAP Online Help

20.07.2007

Slotting Use During slotting, a storage concept is automatically determined for a product. The system determines the underlying storage parameters that are relevant for putaway on the basis of master data, that is, product data, requirement data [Seite 279], and packaging data. These parameters describe the storage section in which the product is to be stored, the properties that the storage bin is to have, and the putaway strategy that is to be used. Slotting takes into account master data that is not dependent on the execution process. If the putaway process for a product is dependent on execution parameters, this dependency is taken into account later on during storage bin determination for putaway [Seite 291]. This does not, however, have an effect on the results of slotting.

Prerequisites ●

You work with storage bin types.

●

You have defined the attributes in the product master that you want to use to determine the storage parameters.

●

You have defined a number range interval and assigned it to your warehouse in Customizing under Extended Warehouse Management → Goods Receipt Process → Slotting → General Settings.

●

You have defined storage type sequences in Customizing under Extended Warehouse Management → Goods Receipt Process → Slotting → Master Data.

●

You have made the settings for the condition technique in Customizing under Extended Warehouse Management → Goods Receipt Process → Slotting → Condition Technique.

●

You have defined condition records. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Slotting → Condition Maintenance for Slotting.

Features During slotting, the system determines the following storage parameters and stores them in the product master: 1. Putaway control indicator (and, optionally, stock removal control indicator) 2. Maximum quantity in storage type 3. Storage section indicator 4. Storage bin types The system always performs step 1. Steps 2 to 4 are optional. Steps 1, 3, and 4 are performed using the condition technique. Step 4 can also be performed using storage bin type determination rules [Seite 283]. For more information about the condition technique, see the SAP Library under mySAP Customer Relationship Management → CRM Enterprise → Enterprise Sales → Sales Management for Commercial and Industrial Customers → Basic Functions → Condition Technique. Slotting is optional. We recommend that you perform it periodically in the background. The results of slotting can be used in storage bin determination. Slotting also forms the basis of rearrangement [Seite 287].

SAP Extended Warehouse Management (SAP EWM)

510

277

SAP Online Help

20.07.2007

Activities To perform slotting, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Slotting → Slot Products for Warehouse. Then choose the storage parameters that the system is to determine.

SAP Extended Warehouse Management (SAP EWM)

510

278

SAP Online Help

20.07.2007

SAP APO Interface for Transferring Requirement Data To be able to calculate parameters such as the maximum quantity in the storage type, slotting needs requirement data for the relevant product. This requirement data can come from SAP Advanced Planning and Optimization (SAP APO). Extended Warehouse Management (EWM) stores this information locally in the product master (on the Slotting tab page, Requirement/Demand Data area). You can also fill these local attributes in EWM with data from other sources. To do this, you have several processing options in the product master, for example, manual input or mass maintenance. SAP APO and EWM manage requirement data at different organizational levels. SAP APO performs planning processes for locations of the type Plant. EWM stores requirement data at warehouse number level. Slotting assumes that a 1:1 relationship exists between the SAP APO location and the EWM warehouse number. If the relationship is not 1:1, you can use Business Add-Ins (BAdIs) for the conversion. In most cases, SAP APO and EWM run on different systems. The calling EWM system needs information about the SAP APO instance such as: ●

Logical system

●

Time interval for which the system is to read requirement data

●

Information as to whether the data is forecast data or historical data

You define this information in Customizing for EWM. For more information, see the Implementation Guide (IMG) under Goods Receipt Process → Slotting → General Settings → Change Information for APO Instances. If you have set the following indicators on the selection screen for slotting, the system reads the requirement data from SAP APO when performing slotting: ●

Update Requirement Quantity

●

Update Number of Order Items

●

Update Recommended Storage Qty

You can also read the requirement data as a separate process.

SAP Extended Warehouse Management (SAP EWM)

510

279

SAP Online Help

20.07.2007

Update of Results in Product Master Use The system updates the results of the slotting run in the product master.

Features All the product attributes that form the slotting results exist twice in the product master: ●

As active values

●

As planned values (can be recognized due to their name)

The exact values that are updated when the results are updated depends on the save mode that you chose when you called slotting: ●

Do Not Save Results We recommend that you use this option if you have performed slotting interactively and you want to analyze the results. If you have performed slotting in the background, you can analyze the log, but you cannot see the results directly.

●

Save Results (The system only updates the planned values in the product master.) Depending on the storage bin and stock situations, it can be useful to save the results of slotting as planned values only. The system only keeps the planned values for a possible activation, and does not use them in storage processes.

●

Save and Activate Results (The system updates both the planned values and the active values in the product master.) The system updates the results of slotting in the fields for the planned values and the active values in the product master. These new values are then available immediately for all storage processes.

Product Attribute Levels The product master has various views that represent various levels of product attributes: ●

Global views

●

Warehouse-number-dependent views

●

Storage-type-dependent views

Before a slotting run, only a global view must exist for the product, in other words, the product must be known in the system. The system either creates the warehouse-number-dependent views and storage-type-dependent views when updating the results in the product master or it updates them if they existed already.

Fixing Values You can use a relevant indicator to fix all product attributes that can form the results of slotting. In this case, the system does not overwrite these attributes during slotting.

SAP Extended Warehouse Management (SAP EWM)

510

280

SAP Online Help

20.07.2007

Update Attribute Storage Bin Improvable Use Slotting determines the optimum storage type, storage section, and storage bin type for a product. The system can determine whether a certain stock (quant) is stored in an optimum way. To do this, it compares these optimum values with the attributes of the storage bin in which the quant is located. Since the attribute Storage Bin Improvable depends on product attributes and on the current storage bin, it exists in both the fixed bin table and in the quant.

Instances of the Attribute Storage Bin Improvable The attribute has the following instances: ●

Not Improvable ( ) All three attributes (storage type, storage area, and storage bin type) are optimum.

●

Pick with Priority (A) You can use this instance to support campaigns. You must configure this process manually. If a significantly greater demand is expected for a product during a campaign, you can create additional new fixed storage bins (picking bins) and can choose the instance Pick with Priority for these bins. You should also adjust the maximum storage type quantity of the relevant storage type for the product, or deactivate the check. This instance is independent from the other instances and it is never set automatically by slotting.

●

Improvable (B) One of the three attributes (storage type, storage section, or storage bin type) is not optimum. The criteria for the instance Storage Type Improvable (C) are not met.

●

Storage Type Improvable (C) The storage section and storage bin type are optimum. The current storage type belongs to a storage type group. The storage type is optimum for the product within the group but it is not optimum on a global level. In other words, the storage type group is not first in the search sequence.

Update When you save or activate the results of slotting for a product, the system updates the attribute Storage Bin Improvable for the following in the warehouse number: ●

For all quants of the product within the warehouse number

●

For all existing and any newly-assigned fixed storage bins for the product within the warehouse number

The system determines the attribute Storage Bin Improvable for the new quant in the destination storage bin for each stock movement within the warehouse where the destination storage type has the storage type role Standard Storage Type.

SAP Extended Warehouse Management (SAP EWM)

510

281

SAP Online Help

20.07.2007

Consideration of Storage Types In slotting, the system determines attributes for a subset of storage types only. These storage types are assigned to a warehouse number. You define the relevant storage types in Customizing for EWM (Extended Warehouse Management) by using the Warehouse No. and PutawayControlInd key fields. For more information, see the Implementation Guide (IMG) under Goods Receipt Process → Slotting → Master Data → Define Putaway Control Indicator. You have assigned a storage type search sequence to the putaway control indicator in Customizing for EWM. The search sequence can contain storage types or storage type groups.

Storage Types The system interprets each storage type as an independent area in the warehouse (for example, reserve or picking area). It assumes that stock for a product is to be stored in each storage type.

Storage Type Groups The storage types in a storage type group have an equal weighting. The system assumes that a product is to be stored in one storage type only within a group. If, therefore, the system considers the storage type group for a certain product, there can be a prioritization of the storage types within this group in relation to this product. The system uses the optimum storage bin type per storage type for the prioritization. It determines an optimum storage bin type from the potential storage bin types for each storage type. It then prioritizes the optimum storage bin types again. When doing this, the system uses the same criteria as it used to determine the optimum value within a storage type. The sequence of storage bin types produces the sequence of storage types. The systems updates the position of a storage type in accordance with the prioritization in the product master in the storage type view in the Putaway Sequence attribute. It then uses this information when creating warehouse tasks (WTs).

Skip Storage Type If the system could not determine the optimum storage section indicator or the optimum storage bin type during slotting, it does not consider the storage type when creating a WT. This system does this by setting the Skip During Putaway indicator in the storage type view of the product master. In this case, the system does not set the following attributes: ●

Min. Replenish. Qty (Minimum Replenishment Quantity)

●

Plnd Min. Replen. Qty (Planned Minimum Replenishment Quantity)

●

Maximum Quantity

This also means that replenishment cannot take place in this storage type.

SAP Extended Warehouse Management (SAP EWM)

510

282

SAP Online Help

20.07.2007

Use of Storage Bin Type Determination Rules Use There are two options for determining the optimum storage bin type in slotting: ●

Using the condition technique (in the same way as determining the putaway control indicator and the storage section indicator)

●

Using storage bin type determination rules

The option that the system uses depends on the parameters that you have defined at storage type level for slotting.

Prerequisites In Customizing for Extended Warehouse Management (EWM), you have defined whether you want to work with the condition technique or with storage bin type determination rules. In the latter case, you have chosen the required storage bin type determination rule. For more information, see the Implementation Guide (IMG) for EWM under Goods Receipt Process → Slotting → General Settings → Define Storage Type Parameters for Slotting.

Features The following storage bin type determination rules are available: ●

Maximum Weight

●

Capacity Factor: Material

●

Simple Volume Check

●

Simple Dimension Check The system compares the dimensions of the relevant packing level (PL) with the dimensions of the storage bin type (BT) in accordance with the following logical expression: Length (PL) < Length (BT) AND Width (PL) < Width (BT) AND Height (PL) < Height (BT) The system calculates the maximum number of packages by dividing the length, width, and height of the storage bin type by the length, width, and height of the packing level. The result is a maximum number per dimension. The global maximum number is then the product of the three maximum values per dimension.

●

Dimension Check with Z-Axis Rotation The system compares the dimensions of the relevant packing level with the dimensions of the storage bin type in accordance with the following logical expression: Length (PL) < Length (BT) AND Width (PL) < Width (BT) AND Height (PL) < Height (BT) OR Length (PL) < Width (BT) AND Width (PL) < Length (BT) AND Height (PL) < Height (BT) The system calculates the maximum number of packages as described in the section Simple Dimension Check for each of the two orientations allowed. The global maximum number is then the greater of the two maximum values per orientation.

SAP Extended Warehouse Management (SAP EWM)

510

283

SAP Online Help ●

20.07.2007

Dimension Check with Rotation and Tilt The system compares the dimensions of the relevant packing level with the dimensions of the storage bin type in accordance with the following logical expression: Length (PL) < Length (BT) AND Width (PL) < Width (BT) AND Height (PL) < Height (BT) OR Length (PL) < Length (BT) AND Width (PL) < Height (BT) AND Height (PL) < Width (BT) OR Length (PL) < Width (BT) AND Width (PL) < Length (BT) AND Height (PL) < Height (BT) OR Length (PL) < Width (BT) AND Width (PL) < Height (BT) AND Height (PL) < Length (BT) OR Length (PL) < Height (BT) AND Width (PL) < Length (BT) AND Height (PL) < Width (BT) OR Length (PL) < Height (BT) AND Width (PL) < Width (BT) AND Height (PL) < Length (BT) The system calculates the maximum number of packages as described in the section Simple Dimension Check for each of the six orientations allowed. The global maximum number is then the greatest of the six maximum values per orientation.

●

Weight Check and Simple Volume Check

●

Weight Check and Simple Dimension Check

●

Weight Check and Dimension Check with Z-Axis Rotation

●

Weight Check and Dimension Check with Rotation and Tilt

Additional Parameter Dimension Ratio The product master attribute Dimension Ratio (on the Slotting tab page) considers the ratio between the length, width, and height of the relevant packing level. The system calculates all the ratios between length, width, and height that make sense on the basis of the orientations allowed. Orientations are not permitted in cases where the calculated ratio exceeds the parameter value from the product master. The system uses the dimension ratio in the following storage bin type determination rules: ●

Simple dimension check (one orientation)

●

Dimension check with z-axis rotation (two orientations)

●

Dimension check with rotation and tilt (six orientations)

●

Weight check and simple dimension check

●

Weight check and dimension check with z-axis rotation

SAP Extended Warehouse Management (SAP EWM)

510

284

SAP Online Help ●

20.07.2007

Weight check and dimension check with rotation and tilt

SAP Extended Warehouse Management (SAP EWM)

510

285

SAP Online Help

20.07.2007

Simulation of Slotting Use You can use this function to simulate slotting without updating the product master.

Features You perform the simulation in the test system. There you can change the configuration in any way that you want to without causing errors. You can analyze the results of the simulation step-by-step and can optimize the configuration. When you are satisfied with the result, you must adapt the configuration in the production system in accordance with the configuration in the test system. Part of the configuration is mapped via master data that you must change manually in the production system. We recommend that you then simulate slotting in the production system to check the configuration. Afterwards, you can perform slotting in the production system, and can save and activate the results there.

Activities ●

To simulate slotting, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Slotting → Slot Products for Warehouse.

●

To activate the plan values or to simulate the activation of plan values, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Slotting → Activate Plan Values. You cannot perform slotting runs in this transaction. You can only display and activate the results from a slotting run that you have performed interactively or in the background. You can also simulate the activation of these results.

SAP Extended Warehouse Management (SAP EWM)

510

286

SAP Online Help

20.07.2007

Rearrangement Use You can use rearrangement to optimize the arrangement of your products in the warehouse by moving stock such as fast-moving items to the relevant optimal storage bin.

Prerequisites ●

You have created products and stocks.

●

You have defined a default warehouse process type in Customizing for Extended Warehouse Management (EWM) under Internal Warehouse Processes → Warehouse Optimization → Specify Default Warehouse Process Type for Rearrangement.

●

You have made the Customizing settings for putaway.

●

If you want to work with slotting indexes, you must enter a value in the following places in the Evaluate Whse Item field in Customizing for EWM under Goods Receipt Process → Strategies: ○

Storage Type Search → Assign Storage Types to Storage Type Search Sequence

○

Storage Section Search → Maintain Storage Section Search Sequence

○

Storage Bin Determination → Alternative Storage Bin Type Sequence or HU Types → Define HU Types for Each Storage Bin Type

Features The system compares the current storage type, storage section, and storage bin type with the optimal parameters from slotting [Seite 277]. When doing this, it analyzes how well suited the current parameters (storage type, storage section, and storage bin type) are to the product. If they are not optimal, the system proposes an optimum storage bin. When searching for an optimum destination storage bin (destination storage bin determination), the system uses search sequences for storage types, storage sections, and storage bin types. The entries in the search sequences are sorted by the slotting index and in descending order. You can assign a slotting index for each step in a search sequence in Customizing. The first entry in a search sequence should not have a slotting index so that a storage bin with an optimum storage type, storage section, and storage bin type has a slotting index of zero. In the case of rearrangement, the system first tries to propose an optimum storage bin (with a slotting index of zero). If this is not possible, the system proposes an alternative storage bin with the next lowest slotting index. The system only proposes an alternative storage bin if its slotting index is lower than that of the current storage bin. You can identify the most urgent stock transfers on the basis of the following data: ○

Slotting index of the current storage bin

○

Difference between the slotting indexes of the proposed storage bin and the current storage bin

The system also displays the number of empty bins per storage type, storage section, and storage bin type as part of the analysis. For an example of rearrangement, see here [Seite 289].

SAP Extended Warehouse Management (SAP EWM)

510

287

SAP Online Help

20.07.2007

Activities 1. To start rearrangement, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Rearrangement. 2. Choose the required stocks. The system performs the analysis and displays the number of stock items per optimal storage bin type, storage section, and storage bin type/storage section for each current storage bin type, storage section, and storage bin type/storage section. 3. Choose one of the analyses, the required cell, column, or row, and then Details. 4. In the detail view, choose the required stock item and create a warehouse task. The system proposes a destination storage bin and reserves it. Save the warehouse task.

Alternatively, you can create a warehouse request to plan rearrangement as a wave. In this case, the system does not adopt the proposed destination storage bin and does not reserve it.

You can also execute rearrangement in the background. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Rearrangement (Background).

SAP Extended Warehouse Management (SAP EWM)

510

288

SAP Online Help

20.07.2007

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

Storage Section for Slow-Moving Items Storage Section for Fast-Moving Items (Golden Zone)

Entrance

Exit

The second figure shows a typical pick path before rearrangement takes place. Since some of the storage bins containing the products to be picked are situated a long way from the central aisle in the area for slow-moving items, the picker sometimes has to drive a long way down the side aisles to pick the required products.

Entrance

SAP Extended Warehouse Management (SAP EWM)

Exit

510

289

SAP Online Help

20.07.2007

The third figure shows how the system tries to shorten this long pick path during rearrangement by proposing that the fast-moving products are moved to the area for fastmoving items.

Entrance

Exit

The fourth figure shows the pick path after rearrangement has taken place. During picking, fast-moving items are often picked. Since these are now closer to the central aisle, the pick path is shorter. Now the picker rarely has to drive down a side aisle to pick products.

Entrance

SAP Extended Warehouse Management (SAP EWM)

Exit

510

290

SAP Online Help

20.07.2007

Storage Bin Determination for Putaway Use The aim of storage bin determination is to find the best physical destination storage bin for a putaway process or an internal warehouse goods movement. In addition to other data, parameters from the product master that you have defined manually or that were determined in slotting [Seite 277] are used to do this. Storage bin determination for putaway occurs automatically when a warehouse task is generated.

Prerequisites ●

You have created storage bins.

●

You have made the settings for putaway in Customizing for Extended Warehouse Management (EWM), for example: ○

You have defined storage section search sequences under Goods Receipt Process → Strategies → Storage Section Search → Maintain Storage Section Search Sequence.

○

You have defined HU types for each storage bin type under Goods Receipt Process → Strategies → Storage Bin Determination → HU Types → Define HU Types for Each Storage Bin Type.

Features During storage bin determination, a physical storage bin is determined by means of determining and applying the suitable strategies [Seite 375].

In a fixed storage bin scenario, it could be the case that the fixed storage bin has already been determined for a storage type by slotting. In this case, you do not need to determine and apply additional search sequences. In a putaway process, storage bin determination covers the following steps: Determination of storage types The system first determines the storage type by determining and applying a storage type search sequence. The storage type search sequence defines in which storage types and in which order the system is to search for a destination storage bin for putaway. You can define multiple accesses for determining the storage type search sequence. The system checks these accesses until it finds a suitable storage type search sequence. You assign a putaway rule to each storage type in the storage type search sequence. The putaway rule specifies how a storage bin is to be determined, for example, empty storage bin. In addition to the putaway rule, the storage behavior also plays a role. It describes the type of storage bins, for example, normal, bulk storage, or pallet storage.

If a product has the stock category Quality Inspection, it could be the case that all other parameters are unimportant. You could, therefore, define the first access in such a way that the system is to search for a storage type search sequence where only this stock type is used. Determination of storage sections

SAP Extended Warehouse Management (SAP EWM)

510

291

SAP Online Help

20.07.2007

For each storage type that is found, the system then determines a storage section by determining and applying a storage section search sequence. You can use the Business AddIns in the /SCWM/ES_CORE_PTS enhancement spot to implement a customer-specific logic. Determination of storage bin types Then the system determines a storage bin type for each storage type by determining and applying a storage bin type search sequence. You can use the Business Add-Ins in the /SCWM/ES_CORE_PTS enhancement spot to implement a customer-specific logic. Determination of storage bins Last of all, the system uses a certain priority to evaluate the combinations of storage type, storage section, and storage bin type that have been found. Here it tries to find a storage bin for each combination in accordance with the putaway rule. Slotting and storage bin determination If you use slotting, it could be the case that you want to prevent storage bin determination for products that have not yet been slotted. If, however, you do not use slotting, there is no reason to prevent storage bin determination. You can also use the IMG activity Define Warehouse Number Parameters for Putaway (under Goods Receipt Process → Strategies) to control at warehouse level whether storage bin determination is to be permitted if slotting has not yet been performed for a product.

SAP Extended Warehouse Management (SAP EWM)

510

292

SAP Online Help

20.07.2007

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

Integration See Creation of Inspection Document [Seite 869]

Prerequisites ●

You have carried out the Customizing for creating inspection documents [Seite 869].

●

You have defined inspection rules (see Master Data [Seite 855]).

●

In the delivery, you have specified all the data necessary for the creation of an inspection document. If not all of the necessary data exists in the delivery by the time at which EWM is to create the inspection documents, EWM creates the inspection documents later. For example, EWM is to create an inspection document when the inbound delivery is activated. The batch number is required for creation. EWM only creates the inspection document once you have specified the batch number.

Features In the following cases, EWM creates inspection documents in the background, regardless of Customizing: ●

If you or EWM activate an inbound delivery

●

If EWM sets the status In Yard for an inbound delivery

●

Before EWM creates a warehouse task

●

Before you post the goods receipt

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

SAP Extended Warehouse Management (SAP EWM)

510

293

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

294

SAP Online Help

20.07.2007

Counting Use The aim of counting is to check the quality of a sample of inbound deliveries. This means that counting is a quality assurance measure in the goods receipt process that you can use to ensure consistency between the quantities entered in the system and the actual quantities.

Integration ●

The Quality Inspection Engine [Seite 888] (QIE), an integral part of the SCM system, provides essential functions that enable a system-supported check (counting) in the inbound delivery process.

●

Integration with an ERP system is required to enable inbound delivery notifications to be created automatically in Extended Warehouse Management (EWM).

Prerequisites General settings for counting ●

You have implemented the QIE and executed the following in Customizing for EWM under Cross-Process Settings → Quality Management: ○

You have assigned decision codes to decision groups.

○

You have defined which of the available properties of the inspection object types the system is to use as dynamic criteria when creating the inspection document.

○

You have defined a percentage that specifies how many delivery items are to be counted.

○

You have checked that the inspection object types and their properties have been activated.

●

You have defined quantity intervals and value intervals in Customizing for EWM under Goods Receipt Process → Counting.

●

You have defined inspection rules. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Quality Management → Maintain Inspection Rule.

Additional settings for explicit counting Storage control ●

●

You have defined the following in Customizing for EWM under Cross-Process Settings → Warehouse Task → Define Process-Oriented Storage Control: ○

Storage types and storage bins (basis of the counting station)

○

External storage process steps

○

Definition of the storage process

You have defined warehouse process types and control indicators for determining warehouse process types in Customizing for EWM under Cross-Process Settings → Warehouse Task.

SAP Extended Warehouse Management (SAP EWM)

510

295

SAP Online Help ●

20.07.2007

You have defined warehouse products. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Product → Maintain Warehouse Product.

Counting station ●

You have defined a work center for counting (counting station). To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Work Center → Define Master Data Attributes.

Features When you change or activate an inbound delivery notification, the system first determines whether the delivery items are to be counted. To do this, it checks if an active inspection object type and inspection rule exist. Inspection object types define the inspection process. You use the inspection rule to define when a delivery item is to be counted. To do this, you draw on certain inbound delivery notification properties: ●

Warehouse number

●

Document type of the delivery

●

Partner (supplier)

●

Product

●

Quantity interval

●

Value interval

If a valid inspection rule exists, the system creates an inspection document, taking into account the dynamic criteria. It marks the relevant delivery item for counting. You then perform counting either explicitly or implicitly: ●

Explicit counting You must enter the count results for the products at the counting station. The system determines the storage bin (storage type) for this counting station on the basis of the storage control settings. You can perform explicit counting only for handling units.

●

Implicit counting The information specifying that a product must be counted is part of the warehouse task data. If a difference is determined, you must confirm the warehouse task with differences (exception code) to end the transaction. You can perform implicit counting only for unpacked products.

Activities Explicit counting ...

1. You have changed or activated an inbound delivery notification in EWM. The system has found an active inspection object type and an inspection rule, and has created an inspection document. Create a warehouse task with reference to the inbound delivery and confirm it. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task for Warehouse Request → Putaway for Inbound Delivery. The system uses the storage control settings to determine the storage bin for counting for all the delivery items with an inspection document. If the system had not created an inspection document because an active inspection object type and inspection rule were not available, the delivery items would be put away immediately at the final storage bin.

SAP Extended Warehouse Management (SAP EWM)

510

296

SAP Online Help

20.07.2007

2. Call the counting station that is assigned to the storage bin for counting and enter the count results. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Quality Inspection and Count. Implicit counting ...

You have changed or activated an inbound delivery notification in EWM. The system has found an active inspection object type and an inspection rule, and has created an inspection document. Create a warehouse task with reference to the inbound delivery, confirm the count results, and confirm the warehouse task. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task for Warehouse Request → Putaway for Inbound Delivery. The delivery items are put away immediately at the final storage bin.

SAP Extended Warehouse Management (SAP EWM)

510

297

SAP Online Help

20.07.2007

Deconsolidation Use You can use this function to divide up a deconsolidation handling unit (deconsolidation HU) across multiple putaway HUs. This is necessary if a deconsolidation HU contains different products that you want to put away in different storage sections.

Integration You define the consolidation groups [Extern] in Customizing for storage control [Seite 334]. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Define Consolidation Group.

Prerequisites ●

If EWM is to define a deconsolidation, one of the following cases must be present:

...

○

The activity areas for the products within an HU are different.

○

The activity areas for the products within an HU are the same, but the consolidation groups are different.

○

The activity areas and consolidation groups for the products within an HU are the same, but the maximum number of warehouse tasks for the HU has been exceeded.

●

In Customizing, you have defined activity areas. For more information, see the IMG for EWM under Master Data → Define Activity Area.

●

In Customizing, you have defined deconsolidation rules. For more information, see the IMG for EWM under Goods Receipt Process → Deconsolidation.

●

If you want to use deconsolidation in process-oriented storage control, you must have defined the deconsolidation attributes for each activity area. For more information, see the IMG for EWM under Goods Receipt Process → Deconsolidation → Define Attributes for Deconsolidation for Each Activity Area.

Features When EWM performs deconsolidation, it creates a warehouse task for each HU item, which deconsolidation then takes into account.

For example, you have a deconsolidation HU HU123 with product PROD1 for the reserve storage area RL, product PROD2 for the bulk storage area BL, and product PROD3 for the high rack storage area HL. EWM creates the following warehouse tasks: ●

A warehouse task for the deconsolidation HU

●

A warehouse task for each product, for deconsolidating the deconsolidation HU into three putaway HUs.

●

Other warehouse tasks, depending on your Customizing settings (Direct or Combined Storage Control [Seite 268]).

SAP Extended Warehouse Management (SAP EWM)

510

298

SAP Online Help

20.07.2007

Special Features for Deconsolidation in Cross-Docking When you perform deconsolidation in cross-docking, EWM distributes the contents of the deconsolidation HU as follows: ●

EWM distributes the products in the deconsolidation HU that are not relevant for crossdocking across multiple putaway HUs, as in the standard putaway procedure.

●

EWM distributes the products in the deconsolidation HU that are relevant for crossdocking across multiple pick-HUs.

EWM does not determine the consolidation group of the pick-HUs for products that are crossdocking-relevant from the data of the destination storage bin, rather from the data of the outbound delivery. For example, a consolidation group can correspond to the delivery in such a way that EWM assigns all products that belong to a delivery to a consolidation group as well. For more information about cross-docking, see Cross-Docking [Seite 544].

Activities On the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Deconsolidation in Goods Receipt.

Example You receive a deconsolidation HU with 15 warehouse tasks (WTs), where the destination data is all assigned to the same activity area. You have set the Maximum Number of WTs in the Deconsolidation HU to ten, and the Maximum Number of WTs in the Putaway-HU to five. This means that if you are using process-oriented storage control, EWM forwards the HU to a deconsolidation station, due to the HU exceeding the permitted maximum number of WTs in the deconsolidation HU. During deconsolidation at this location, EWM creates putaway-HUs. After you have confirmed the repacking of five product-WTs into the putaway-HU, EWM proposes this HU for closure, due to the parameter Maximum Number of WTs in the Putaway-HU. This means that it also releases the HU for the following process step Putaway.

SAP Extended Warehouse Management (SAP EWM)

510

299

SAP Online Help

20.07.2007

Putaway Use The destination of the final putaway is the putaway of products into storage bins in the warehouse. The starting point for this is the warehouse request [Seite 109]. For the putaway, Extended Warehouse Management (EWM) determines a putaway path. EWM uses your settings to define the path that the warehouse employee should take to put the products away. Regardless of how you perform putaways in your company, you can configure EWM in such a way that the putaway activities are performed in one of the following ways: ●

Automatically during creation of an inbound delivery

●

Regularly at specific times

●

Manually using overviews of the daily loads, after a request from an employee

You specify this using the Post Processing Framework. For scheduling and monitoring of the putaway operations, EWM stores a putaway status in each delivery item. This status tells you, for example, for which items putaway has already started.

Integration Putaway uses the following: ●

Putaway strategies [Seite 375]

●

Slotting [Seite 277]

●

Storage control [Seite 334]

Features ●

You can perform the final putaway using radio frequency devices (RF devices), or you can print the warehouse orders and enter the information for the final putaway manually. You can then enter and save the manually entered data in EWM. Both on the RF device’s display and on the paper printout, the sequence of the warehouse tasks corresponds to the putaway path.

●

If there are unplanned stock movements without a preceding document, you can create a warehouse request without a reference.

●

If, for example, the connection between SAP R/3 and EWM is interrupted, you can create a warehouse request manually. SAP R/3 and EWM compare their data at a later point when the connection is available again.

●

You can use EWM to allow the system to define a putaway path for the putaway, which optimizes the order of the storage bins. Storage bin sorting takes place in a logical section of the warehouse, the Putaway activity area, and refers to specific activities. When defining this path, EWM takes into account both one-way streets as well as differentiations in the various putaway strategies, for example, first drive to all the righthand bins, then to all the left-hand bins, or first drive to the standard bins, then to the reserve bins.

Warehouse Tasks for Putaway Putaway creates warehouse tasks for you, for the purpose of putting away your products. The warehouse tasks can be created in the following ways:

SAP Extended Warehouse Management (SAP EWM)

510

300

SAP Online Help ●

20.07.2007

Automatically by EWM You can control the time by assigning a schedule condition in the Post Processing Framework Action (PPF Action). For example, Status Packed is Set or Status Goods Receipt is Set.

●

Manually by a user

Putaway requires warehouse tasks in order to ●

Specify the destination storage types, sections, and bins

●

Specify the storage control for the destination storage type For more information about storage control, see Process- and Layout-Oriented Storage Control [Seite 334].

When EWM creates a warehouse task for putaway, it simultaneously checks whether the product to be put away is a hazardous substance [Extern]. If the product is a hazardous substance, EWM determines (according to your Customizing) the storage type you can use to put away the hazardous substance. For more information, see Hazardous Substance Master [Seite 969].

Activities If you want to use RF devices, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Log On to RF Environment. If you want to print the warehouse order, you can define this in Customizing. For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Order → Print.

SAP Extended Warehouse Management (SAP EWM)

510

301

SAP Online Help

20.07.2007

Creation of Warehouse Tasks for Putaway Use Extended Warehouse Management (EWM) automatically creates warehouse tasks [Seite 112] for the putaway based on a warehouse request for an inbound delivery [Seite 405], so that you can put away products. EWM uses a warehouse task to specify the following for the putaway: ●

The destination storage types, sections, and bins

●

The path to the destination storage type

Prerequisites If you want EWM to automatically group warehouse tasks into warehouse orders, you must have made the settings in Customizing for warehouse order creation. In the Implementation Guide (IMG) for EWM, choose Cross-Process Settings → Warehouse Order.

Features ●

EWM can create warehouse tasks for an inbound delivery in the following ways: ○

EWM automatically creates warehouse tasks for an inbound delivery, using an action from the Post Processing Framework (PPF).

○

You create the warehouse tasks manually.

●

When EWM creates a warehouse task for a warehouse request, it uses putaway strategies [Seite 375] to determine the storage bin. For more information, see Storage Bin Determination for Putaway [Seite 291].

●

When EWM creates a warehouse task, it uses direct or combined storage control [Seite 268] to determine whether you should put away a handling unit directly or by using interim storage bins. The warehouse task reflects the direct or combined storage control.

●

EWM automatically groups warehouse tasks according to your Customizing settings for warehouse orders. For more information, see Warehouse Order Creation [Seite 419]

●

EWM uses layout-oriented and process-oriented storage control, according to your Customizing settings. For more information, see Process-Oriented Storage Control [Seite 336] and Layout-Oriented Storage Control [Seite 340].

●

In the warehouse task, EWM specifies various activities for you to perform (for example, deconsolidation [Seite 298]), according to your Customizing settings.

Activities ●

If you have made settings in Customizing for PPF for the PPF action to create warehouse tasks for putaway, EWM automatically creates the warehouse task for putaway. In the IMG for EWM, choose Cross-Process Settings → Delivery Processing → Actions → Use Assistant to Create Actions.

SAP Extended Warehouse Management (SAP EWM)

510

302

SAP Online Help

20.07.2007

●

If you want to create a warehouse task manually, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task for Warehouse Request → Putaway for Inbound Delivery.

●

If you want to post goods receipts for all deliveries for an inbound delivery, and also want to create warehouse tasks for unloading, on the SAP Easy Access screen, choose Extended Warehouse Management → Goods Receipt and Shipping → Unload.

●

When EWM creates a warehouse request warehouse task for an outbound delivery, it simultaneously updates this warehouse request. EWM carries out this update by updating the quantity in the document flow. If the quantity update leads to a change in status, EWM updates this change in the warehouse request as well.

You have an inbound delivery of 100 pieces of a product. EWM automatically creates three warehouse tasks (WT1, WT2, and WT3) for the entire quantity, based on the storage bin determination. Following creation of the warehouse tasks, the warehouse request status Putaway Planning changes to Completed. If EWM does not create warehouse tasks for the entire quantity, the Putaway Planning status is set to Partially Completed. The following table gives you an overview of the Putaway Planning status in the warehouse request. Goods Receipt Process Product description

Delivery Item

Warehouse Task

P-01

10

WT1 for 10 pieces

P-01

20

WT2 for 30 pieces

P-01

30

WT3 for 60 pieces

Putaway Planning Partially Completed Partially Completed Completed Warehouse Request Status

, after EWM creates

WT1

, after EWM creates

WT2

, after EWM creates WT3

SAP Extended Warehouse Management (SAP EWM)

510

303

SAP Online Help

20.07.2007

Specification of the Putaway Path Use You can use this function to specify a putaway path for each activity in the activity area. When Extended Warehouse Management (EWM) creates a warehouse request (WT), it specifies this putaway path. During definition of putaway paths, you can assign more than one putaway path, or you can allow activity areas to overlap. However, only one putaway path is active for each WT.

Integration Specification of the putaway path is integrated into WT processing, which means that EWM sorts the WTs according to the putaway path.

Prerequisites ●

You have defined the storage bin types, descriptions, and structure. For more information, refer to the Implementation Guide (IMG) for EWM under Master Data → Storage Bins.

●

You have defined activity areas and categories, have assigned storage bins to the activity areas, and have specified the sorting sequence of the activity areas. For more information, see the IMG for EWM under Master Data → Activity Areas.

●

You have assigned an activity to a warehouse process type. For more information, see the IMG for EWM under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type.

Features If EWM has grouped several WTs into a warehouse order, then it sorts the WTs based on the warehouse order. This is not dependent on the product that is contained in the handling unit. If you use radio frequency devices, you can skip a destination storage bin proposed by EWM. EWM places this destination storage bin at the end of the RF display.

You cannot gain access to a destination storage bin because a colleague is currently putting away products in it. You skip the destination storage bin proposed by EWM and process the next one.

Activities ...

For your putaway, you or EWM create the necessary WTs for the warehouse request of the outbound delivery. In so doing, EWM determines the putaway path according to your settings in Customizing and saves this information in the WT. On the radio frequency device, EWM shows the destination storage bins in this predefined sequence.

Example The following figure shows you an example of specification of the putaway path, based on a warehouse order.

SAP Extended Warehouse Management (SAP EWM)

510

304

SAP Online Help

20.07.2007

EWM has created a warehouse order that contains WTs. It has created a WT for each handling unit item. EWM creates the following putaway path: Document Item

Handling Unit

1

1

2

2

3

1

4

2

5

3

…

…

Therefore, if you simultaneously put away several HUs, EWM sorts these across the warehouse.

SAP Extended Warehouse Management (SAP EWM)

510

305

SAP Online Help

20.07.2007

Putaway Using Radio Frequency Use You can execute putaways using a radio frequency presentation device (RF presentation device).

Prerequisites You have logged on [Seite 790] in the RF environment. The destination storage bins of the warehouse orders [Seite 419] to be processed are always in the same activity area.

Features Putaway According to Handling Unit (HU) You enter a handling unit number (HU number) and the system searches for the corresponding warehouse order or warehouse orders. Putaway According to HU (Collective) You enter more than one HU number and the system searches for the corresponding warehouse orders. Putaway According to Warehouse Order You enter a warehouse order number and the system displays the warehouse tasks assigned to the warehouse order that are to be executed.

Activities Putaway According to Handling Unit (HU) 1. You enter a HU number. EWM thus includes the HU in the resource. 2. The system searches for the corresponding warehouse orders. 3. The system displays the following: ○

If the system finds a WT for the entire HU, the system displays the source data (HU number, destination storage bin).

○

If the system finds WTs for the products in the HU, then you are dealing with a distributive putaway [Extern]. The system displays the first WT it has found according to the sort sequence of the destination storage bins. The system displays the following data: ■

Source HU

■

Product

■

Quantity

■

Batch

■

Destination HU

SAP Extended Warehouse Management (SAP EWM)

510

306

SAP Online Help ■

20.07.2007

Destination storage bin

If a warehouse order has more than one WT, you can do the following: ○

You can skip a WT.

○

You can reverse the sequence in which the system displays the WTs.

○

You can place the displayed WT at the end of the execution.

4. You confirm the data of the HU WT or of the first product WT. 5. If a warehouse order has more than one product WT, the system displays the data of the next product WT and the action repeats itself. Putaway According to Handling Unit (Collective) ...

1. You enter all desired HU numbers. 2. You decide whether you want to putaway further in a guided manner or according to product number or warehouse task. 3. The system searches for the corresponding warehouse task. 4. The further steps correspond to steps three to five for putaway according to handling unit. Putaway According to Warehouse Order ...

1. You enter a warehouse order number. 2. The system searches for the corresponding warehouse tasks. 3. The system displays the source data (product, quantity, batch, and source storage bin) of the first product WT that belongs to the warehouse order, or the source data (HU and source storage bin) of the first HU WT that belongs to the warehouse order. If a warehouse order has more than one WT, you can do the following: ○

You can skip a WT.

○

You can reverse the sequence in which the system displays the WTs.

○

You can place the displayed WT at the end of the execution.

4. You confirm the source data of the first product WT or the source data of the first HU WT. 5. The system displays the destination data of the product WT (product, quantity, batch, and destination storage bin), or the destination data of the HU WT (HU and destination storage bin). 6. You confirm the destination data of the first WT. 7. If a warehouse order has more than one WT, the system displays the source data of the next WT (product WT or HU WT), and the action repeats itself.

Exceptions to Putaway Using RF HU WT Confirmation You can specify an exception for this process and then: ●

Change the destination storage bin

●

In general, skip the HU WT that is currently to be processed For example, if the aisle is blocked, you cannot get to the source storage bin or destination storage bin. During the putaway process, then, the system no longer shows you this HU WT and you do not need to confirm the source data and destination data.

SAP Extended Warehouse Management (SAP EWM)

510

307

SAP Online Help

20.07.2007

Product WT Confirmation You can specify an exception for this process and then: ●

Change the destination storage bin

●

Record differences For example, if a piece of the product quantity is damaged, you can enter a smaller product quantity rather than confirm the quantity.

●

Change the batch

●

In general, skip the product WT that is currently to be processed For example, if the aisle is blocked, you cannot get to the source storage bin or destination storage bin. During the putaway process, then, the system no longer shows you this HU WT and you do not need to confirm the source data and destination data.

SAP Extended Warehouse Management (SAP EWM)

510

308

SAP Online Help

20.07.2007

Manual Assembly of Warehouse Orders Use You use this function in the goods receipt process to delete warehouse tasks of different handling units (HUs) from your warehouse orders, and to group them together in a new warehouse order. This allows you to put away the HUs collectively, and Extended Warehouse Management (EWM) is able to determine the optimal putaway path.

Prerequisites ●

You have made sure that putaway warehouse tasks exist and are active for the entire contents of the HU.

●

If EWM is to generate a single warehouse order for all warehouse tasks that belong to the HUs you have specified, you have made sure that the warehouse activity area and queue for these warehouse tasks are identical (see Warehouse Order Creation [Seite 419]).

●

If you want to print warehouse orders using a PPF action, you have scheduled a corresponding PPF action.

Features This function is optimized so that you can operate it using a hand-held scanner that is installed on a keyboard filter. You can specify multiple HUs in the entry field, one after each other. EWM shows you the specified HU in the lower part of the screen, and assigns the HU to a position field, ascending. For example, you scan three HUs. EWM assigns the HU scanned first to position one, the next HU to position two, and the HU scanned last to position three. Make sure that the position of the HU in EWM matches the physical position of the HU in the resource. When you perform putaway, EWM shows you the position in the Radio Frequency dialog (RF dialog). A traffic light shows the status of the warehouse task. ●

Green means that you have specified a valid HU, and that warehouse tasks exist for all products in the HU. EWM has updated screen content for the total weight and total volume, and increased the number of HUs in the new warehouse order that is to be created by one.

●

Red means that you have specified an HU, but that no warehouse task exists for at least one of the products in the HU. EWM does not update the screen content for the total weight and total volume, and does not include the HU in the new warehouse order that is to be created.

Activities ●

On the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Manually Assemble Warehouse Orders.

●

After you have specified all the HUs, choose Save. In doing this, EWM deletes all warehouse tasks of the HUs from your warehouse orders. EWM attempts to generate a warehouse order for all warehouse tasks, and saves the warehouse tasks in this order. EWM displays a success message if appropriate. If EWM generates one warehouse order only, you can take the warehouse order number directly from the message. If EWM generates multiple warehouse orders, the message only contains the number of warehouse orders. In this case, you can get the warehouse order number from the log. EWM updates the screen content.

SAP Extended Warehouse Management (SAP EWM)

510

309

SAP Online Help ●

20.07.2007

You can print the warehouse order in one of the following ways: ○

Using a Post Processing Framework action

○

Manually Choose Work Center → Print Last Warehouse Order. Under Create Action, choose the PPF action you require for printing warehouse orders (see Printing Warehouse Orders and Warehouse Tasks [Seite 426]).

SAP Extended Warehouse Management (SAP EWM)

510

310

SAP Online Help

20.07.2007

Confirmation Correction Use For example, if you want to change a quantity specification, you can still correct warehouse tasks in the goods receipt process that have already been confirmed.

Prerequisites You have defined a completion delay for inbound deliveries. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Receipt Process → Inbound Delivery → Define Delay in Completing Inbound Deliveries. You are using a document type and item type with a status profile for which you have activated the status DWM. For more information, see the IMG for EWM under Cross-Process Settings → Delivery Processing → Status Management → Define Status Profiles.

Features EWM delays sending a warehouse task that has already been confirmed, corresponding to the completion delay you have specified for inbound deliveries in Customizing. In accordance with the completion delay, you can still correct the actual quantity for the destination storage bin and the batch. You make your correction and specify an exception code in the warehouse task for each delivery item. When the completion delay has passed, EWM sets the status DWM for sending the completion indicator to Completed. By doing this, EWM also indirectly sets the completion status DCO for the inbound delivery to Completed. Only when the completion status DCO for an inbound delivery has status value Completed does EWM forward the confirmed warehouse task to the ERP system. Only now does the ERP system perform any necessary activities, such as for a returns process or a stock transfer order. From this point in time, you cannot make any further corrections in the confirmed warehouse task. You can schedule report /SCWM/R_PRDI_SET_DWM to set the status DWM for sending the completion indicator to Completed. For more information, see the report documentation.

If you do not specify a completion delay for inbound deliveries in Customizing, EWM immediately sets the status DWM for sending the completion indicator to Completed, and you can no longer make a confirmation correction. You can correct a warehouse task that has already been confirmed in both the user interface and in the RF environment [Seite 803]. EWM calculates the difference quantity and posts it.

For example, you have specified 11 pieces as the Act.Qty (Dest.) (destination actual quantity) and already confirmed the warehouse task. You notice that you have made a mistake, and change the Act.Qty (Dest.) to 10 pieces. EWM automatically calculates the Dest.Diff.Qty (destination difference quantity) as 1 piece, and posts this. That is, EWM performs a type of stock adjustment regarding the relevant warehouse task. For displaying the warehouse task in the user interface or in the RF environment, you can use the warehouse order, the stock identification, or the storage bin as a selection criterion.

Activities ...

SAP Extended Warehouse Management (SAP EWM)

510

311

SAP Online Help

20.07.2007

1. If you want to make a confirmation correction using the user interface, on the SAP Easy Access screen choose Extended Warehouse Management → Execution → Confirm Warehouse Task and then Correct the Confirmation. 2. EWM then does the following: a. Checks whether serial numbers are mandatory for the products of the warehouse task You cannot correct the confirmation for products for which a serial number requirement exists. b. Checks which authorizations you have c. Checks whether the warehouse task is locked d. Checks which inbound delivery belongs to the warehouse task (reference) 3. EWM reads the inbound delivery and checks that the completion status DCO of the inbound delivery does not yet have status value Completed. a. If the status does not yet have the status value Completed, EWM locks the inbound delivery from further warehouse activities until you have made your confirmation correction. The fields for the confirmation correction entry are ready for input, and you can make your correction. b. If the status already has the status value Completed, none of the fields are ready for input, and you cannot make a confirmation correction.

SAP Extended Warehouse Management (SAP EWM)

510

312

SAP Online Help

20.07.2007

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

Prerequisites ●

The goods movement bin in the warehouse request into which you are booking the stock for the goods receipt must contain a valid storage bin into which you can book the product.

●

You use an item type that does not contain any of the following status types in the status profile: ○

Planning Putaway

○

Putaway

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

Process ...

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

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

SAP Extended Warehouse Management (SAP EWM)

510

313

SAP Online Help

20.07.2007

Goods Issue Purpose A goods issue [Extern] from Extended Warehouse Management (EWM) is a physical departure of products from your warehouse. With a goods issue posting, you reduce the stock in the warehouse. You can use a goods issue to indicate goods deliveries to your customers. A warehouse request goods issue allows you to display your complex stock removal process steps and includes the following functions: ●

Storage Bin Determination for Stock Removal [Seite 343]

●

Stock Removal [Seite 317]

●

Packing [Seite 506]

●

Loading [Seite 608]

When you display the goods issue process using a warehouse request, you can execute the warehouse-internal processes that precede the actual goods issue, such as picking or packing, within the warehouse before you trigger the actual goods issue posting. The goods issue takes into account your warehouse arrangements, such as stock removal using pick points from a high rack storage area, as well as the process-oriented rules and procedures defined by you, such as packing during warehouse task confirmation. To simplify the search for appropriate stock, EWM offers you stock removal strategies [Seite 396]. You can remove your products from stock either directly or by using storage control [Seite 334]. You can only execute complex stock removal processes by using handling units. You can use the warehouse request to automatically trigger the goods issue processing. To do this, you use the warehouse task as the main document upon which you display all goods movements in EWM.

For more information, see Warehouse Request for Inbound Delivery or Outbound Delivery Order [Seite 112].

Prerequisites ●

The data for the warehouse request for outbound delivery in EWM is complete.

●

You have defined the following basic settings in Customizing for EWM: For examples of basic settings, see Goods Receipt [Seite 263] under Prerequisites.

●

The warehouse request is relevant for picking.

●

You have defined a stock removal strategy in Customizing for EWM under Goods Issue Process → Strategies → Define Stock Removal Strategy.

●

You have defined a stock removal control indicator in Customizing for EWM under Goods Issue Process → Strategies → Define Stock Removal Control Indicator.

Process ... ...

1. EWM receives a goods issue request from another system, for example an SAP system.

SAP Extended Warehouse Management (SAP EWM)

510

314

SAP Online Help

20.07.2007

2. EWM creates a warehouse request for an outbound delivery order [Seite 112], which is the starting point for the goods issue. EWM recognizes, on the item level of the warehouse request, which delivery items are relevant for stock removal with EWM.

For more information, see Creation of a Warehouse Request for an Outbound Delivery Order [Seite 116]. The availability check for the goods issue takes place on the level of the prestored components. EWM does not carry out an independent availability check, but instead assumes a purely executional function. 3. You create a warehouse request for the warehouse request for picking from your warehouse. When you create a warehouse task, the system creates corresponding warehouse orders. These warehouse orders group the warehouse tasks in accordance with the rules defined in Customizing. This means that you receive individual work packages that a worker is to carry out at a certain time (see Warehouse Order Creation [Seite 419]). ○

You can create the warehouse task directly or let EWM create it automatically. EWM can create warehouse tasks in the following manner:

○

■

By default, directly through the release of a wave

■

Automatically, using a Post Processing Framework (PPF) action

You can create the warehouse tasks manually.

For more information, see Creation of Warehouse Tasks for Warehouse Request [Seite 412], Creation of Warehouse Tasks for Stock Removal [Seite 319], or Wave Management [Seite 766]. ○

You can take into account batch information when creating warehouse tasks for picking. If you have not determined the batches to be picked in the warehouse request, and you want to pick one or more batches to cover the required quantity completely, you must verify these batches to the outbound delivery. In doing so, you create a new warehouse request item for each batch.

4. You either print the warehouse request with the warehouse tasks as a list, or you print all individual documents at once. If you remove the goods from the determined source storage bins to the goods issue interface, you can use this printout as the picking document.

For more information, see Printing Warehouse Orders and Warehouse Tasks [Seite 426]. 5. Once you have completed the picking, you confirm the warehouse tasks. 6. You carry out further goods issue activities, such as packing or loading. 7. For each goods issue activity, EWM creates a separate warehouse task, which you confirm after you have completed the physical activity. With this confirmation, you confirm that you have brought the goods to the goods issue interface. This records any stock differences between the required and the picked quantity.

SAP Extended Warehouse Management (SAP EWM)

510

315

SAP Online Help

20.07.2007

For more information, see Handling Differences When Picking for Warehouse Request [Seite 348]. 8. You then post the goods issue for the warehouse request. EWM updates the activity status when a step of the warehouse task processing has been completed. You can inform yourself about the outbound delivery status during the entire goods issue process.

For more information, see Creation of Warehouse Tasks for Warehouse Request [Seite 412].

Using Storage Control

For more information about goods issue processes using storage control, see Storage Control [Seite 334], Layout-Oriented Storage Control [Seite 340] , or Process-Oriented Storage Control [Seite 336].

Results EWM reduces the storage bin stock in the source storage bin by the picked product quantity and posts this quantity to the destination storage bin.

SAP Extended Warehouse Management (SAP EWM)

510

316

SAP Online Help

20.07.2007

Stock Removal Purpose The stock removal process includes the picking of goods from storage bins in the warehouse and preparing them at the destination storage bin. If you use Extended Warehouse Management (EWM) for warehouse management, create a warehouse task [Extern] for all stock movements. You use stock removal transfer orders to execute stock removals. EWM groups stock removal warehouse tasks to warehouse orders. You use the printed warehouse order as a pick list for the stock removal. EWM contains stock removal strategies to simplify your search for the correct product to be removed from stock. According to the stock removal strategy, EWM selects the storage type and exact storage bin from which you can pick the product that is to be removed from stock. Regardless of how you organize stock removals in your company, you can configure EWM in such a way that the stock removal activities are performed in one of the following ways: ●

If EWM creates a warehouse request: automatically, using a Post Processing Framework action.

●

Regularly at set times, using the automatic wave scheduling. For more information, see Automatic Wave Assignment [Seite 773].

Process ...

1. The warehouse request [Seite 109] is a request for EWM to remove goods from stock. For more information, see Warehouse Request for Inbound Delivery or Outbound Delivery Order [Seite 112]. When EWM creates a warehouse request, you can trigger the picking of goods in EWM automatically. In so doing, EWM creates one or more warehouse task items for each item in the warehouse request. EWM automatically transfers the information concerning the picking status to the warehouse order. You then have access to the current data concerning the processing status in the warehouse. 2. You create a warehouse task for the warehouse request. 3. You use a printed warehouse request as the pick list. The warehouse request contains the corresponding warehouse tasks. 4. You confirm the warehouse task. In so doing, you confirm in EWM that the physical removal of goods is concluded. The product that is to be removed from stock is then found at the destination storage bin defined in the warehouse task. At the same time, EWM transfers the picked quantity directly to the corresponding items in the warehouse request. In addition, EWM reduces the storage bin stock in the source storage bin by the picked product quantity and posts this quantity to the destination storage bin.

Example The following graphic clarifies the process of stock removal from the EWM-managed warehouse using a warehouse request:

SAP Extended Warehouse Management (SAP EWM)

510

317

SAP Online Help

Warehouse Request

20.07.2007

Warehouse Task

Warehouse Storage Type 1

Item 1

Warehouse Task 1 Source – Dest. Warehouse Task 2 Source – Dest.

Item 2

Warehouse Task 3 Source – Dest. Warehouse Task 4 Source – Dest.

Storage Type 2

WT 2

WT 3

Warehouse Task 5 Source – Dest. Item 3 Warehouse Task 6 Source – Dest.

WT 4 Goods Issue Zone

To remove the product from stock, you create a warehouse task for a warehouse request to the outbound delivery order. EWM can thus create more than one warehouse task from one item in the warehouse request. This is the case, for example, if you have to pick the product for item 2 of the warehouse request from three different source storage bins to remove the product quantity specified in the warehouse request. Item 2 of the warehouse request results in the three warehouse tasks 2, 3, and 4. You use warehouse tasks 2 and 3 to move the products from storage type 1 to the goods issue zone, and you use warehouse task 4 to move products from storage type 2 to the goods issue zone.

SAP Extended Warehouse Management (SAP EWM)

510

318

SAP Online Help

20.07.2007

Creation of Warehouse Tasks for Stock Removal Use Extended Warehouse Management (EWM) creates warehouse tasks [Seite 112] for stock removal based on a warehouse request for outbound delivery request [Seite 405], so that you can remove products from stock. EWM uses a warehouse task to specify the following for the stock removal: ●

The source storage types, sections, and bins

●

The path to the destination storage type

Prerequisites If you want EWM to automatically group warehouse tasks into warehouse orders, you must have made the settings in Customizing for warehouse order creation. For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Order.

Features ●

EWM can create warehouse tasks for an outbound delivery in the following ways: ○

As default, EWM creates warehouse tasks for an outbound delivery when you or EWM release a wave.

○

EWM automatically creates warehouse tasks for an outbound delivery, using an action from the Post Processing Framework (PPF).

○

You create the warehouse tasks manually.

●

When EWM creates a warehouse task for a warehouse request, it uses stock removal strategies [Seite 396] to determine the storage bin. For more information, see Storage Bin Determination for Stock Removal [Seite 343].

●

When EWM creates a warehouse task, it uses direct or combined storage control [Seite 268] to determine whether you should remove a handling unit from stock directly or by using interim storage bins. The warehouse task reflects the direct or combined storage control.

●

EWM automatically groups warehouse tasks according to your Customizing settings for warehouse orders. For more information, see Warehouse Order Creation [Seite 419]

●

EWM uses layout-oriented and process-oriented storage control, according to your Customizing settings. For more information, see Process-Oriented Storage Control [Seite 336] and Layout-Oriented Storage Control [Seite 340].

●

In the warehouse task, EWM specifies various activities for you to perform (for example, packing) according to your Customizing settings.

Activities ●

If you have made settings in Customizing for PPF for the PPF action to create warehouse tasks for stock removal, EWM automatically creates the warehouse task for stock removal.

SAP Extended Warehouse Management (SAP EWM)

510

319

SAP Online Help

20.07.2007

For more information, see the IMG for EWM, under Cross-Process Settings → Delivery Processing → Actions → Use Assistant to Create Actions. ●

By default, you or EWM create warehouse tasks by releasing a wave. After a wave is generated, it can be released immediately, either automatically or manually depending on the release methods you have defined for the wave or wave template. For more information, see Processing of Waves [Seite 771].

●

If you want to create a warehouse task manually, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task for Warehouse Request → Stock Removal for Outbound Delivery Order.

●

If you create warehouse tasks for a delivery for loading, and then want to post the goods issue, on the SAP Easy Access screen, choose Extended Warehouse Management → Shipping and Receiving → Load.

●

When EWM creates a warehouse request warehouse task for an outbound delivery request, it simultaneously updates this warehouse request. EWM carries out this update by updating the quantity in the document flow. If the quantity update leads to a change in status, EWM updates this change in the warehouse request as well.

You have an outbound delivery of 100 pieces of a product. EWM automatically creates three warehouse tasks (WT1, WT2, and WT3) for the entire quantity, based on the stock determination. Following creation of the warehouse tasks, the warehouse request status Picking Planning changes to Completed. If EWM does not create warehouse tasks for the entire quantity, the Picking Planning status is set to Partially Completed. The following table provides an overview of the Picking Planning status in the warehouse request. Goods Issue Process

Delivery Item

Warehouse Task

Warehouse Request Status Picking Planning

P-01

10

WT1 for 10 pieces

Partially Completed

P-01

20

WT2 for 30 pieces

Partially Completed

P-01

30

WT3 for 60 pieces

Completed

Product description

SAP Extended Warehouse Management (SAP EWM)

510

320

SAP Online Help

20.07.2007

Stock Removal Path Determination Use You can use this function to specify a stock removal path for each activity in the activity area. When Extended Warehouse Management (EWM) creates a warehouse request (WT), it specifies this stock removal path. During definition of stock removal paths, you can assign more than one stock removal path, or you can allow activity areas to overlap. However, only one stock removal path is active for each WT.

Integration Specification of the stock removal path is integrated into WT processing, which means that EWM sorts the WTs according to the stock removal path.

Prerequisites ●

You have defined the storage bin types, descriptions, and structure. For more information, refer to the Implementation Guide (IMG) for EWM under Master Data → Storage Bins.

●

You have defined activity areas and categories, have assigned storage bins to the activity areas, and have specified the sorting sequence of the activity areas. For more information, see the IMG for EWM under Master Data → Activity Areas.

●

You have assigned an activity to a warehouse process type. For more information, see the IMG for EWM under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type.

Features If EWM has grouped several WTs into a warehouse order, then it sorts the WTs based on the warehouse order. This is regardless of which products or HUs are on the storage bins. If you use radio frequency devices, you can skip a source storage bin proposed by EWM. EWM places this source storage bin at the end of the RF display.

You cannot gain access to a source storage bin because a colleague is currently removing products from it. You skip the source storage bin proposed by EWM and process the next one.

Activities ...

For your stock removal, you or EWM create the necessary WTs for the warehouse request for the outbound delivery order. In so doing, EWM determines the stock removal path according to your settings in Customizing and saves this information in the WT. On the radio frequency device, EWM shows the destination storage bins in this predefined sequence.

SAP Extended Warehouse Management (SAP EWM)

510

321

SAP Online Help

20.07.2007

Picking Purpose You can use picking to remove goods from your warehouse for a warehouse request for outbound delivery order [Seite 112]. EWM creates the corresponding warehouse tasks for the warehouse request and assigns them to one or more warehouse orders. You can use the warehouse order as the pick list.

Process ...

1. You or EWM create the warehouse tasks for the outbound delivery. In doing so, EWM uses stock determination to find the required stock. For more information, see Creation of Warehouse Tasks for Stock Removal [Seite 319] or Storage Bin Determination for Stock Removal [Seite 343]. 2. EWM allocates the individual warehouse tasks to a warehouse order and thus builds work packages for the individual warehouse workers. It thereby determines the stock removal path. For more information, see Warehouse Order Creation [Seite 419] and Stock Removal Path Determination [Seite 321]. 3. You can process and confirm the warehouse task as follows: a. You can print the individual warehouse order and process it. You can also process the warehouse orders using radio frequency devices. For more information, see Printing Warehouse Orders and Warehouse Tasks [Seite 426] and Processing Using Radio Frequency [Seite 797]. b. You can pack products during the picking process. For more information, see Pick and Pack During Picking [Seite 323]. c. You can carry out a partial picking or a complete picking. For more information, see Partial Picking [Seite 325]. d. You can enter differences that arise during picking. For more information, see Handling Differences When Picking for Warehouse Request [Seite 348].

Result EWM has created the corresponding warehouse tasks for the warehouse request for an outbound delivery order. You have removed the products from your warehouse, transferred them to the goods issue zone or packing station, for example, and confirmed the associated warehouse tasks.

SAP Extended Warehouse Management (SAP EWM)

510

322

SAP Online Help

20.07.2007

Pick and Pack During Picking Use You can generate pick handling units (pick HUs) into which you can pack products during picking. Extended Warehouse Management (EWM) assigns the pick HU to a warehouse task. You or EWM transfer the pick HUs to the delivery. You thus do not need to execute any further packing for the delivery.

Prerequisites ●

You have created a product that is a packaging material. On the SAP Easy Access screen, choose Master Data → Product → Maintain Product.

●

You have defined a packaging material. In Customizing for EWM, select Cross-Process Settings → Handling Units → Basics → Define Packaging Material.

●

In Customizing, determine which steps you want to execute automatically using EWM.

For more information about making settings in Customizing for the individual steps, see under “Activities“. For more information about packaging materials, see Packaging Materials [Seite 492].

Features In the Implementation Guide (IMG), for the creation of a warehouse order, you can make settings for which packaging material the system should propose for picking. When EWM creates a warehouse order, you can set the packing proposals for any number of combinations of warehouse order, activity area, and movement type, as follows: ●

Automatic creation and assignment of pick HUs When EWM creates a warehouse order, it automatically creates one or more pick HUs with the specified packaging material. It assigns the pick HUs to the warehouse tasks in the warehouse order (optional). When you confirm the associated warehouse tasks, you can manually change the pick HUs and their assignments to the warehouse tasks.

●

Automatic proposal of packaging materials When EWM creates a warehouse order, it automatically proposes the number of pick HUs with the required packaging material. When you confirm the warehouse tasks for the warehouse order, you can confirm the proposals for the packaging materials and manually create your own pick HUs.

●

Manual creation and assignment of pick HUs during warehouse task confirmation EWM does not create any pick HUs, nor does it determine a packaging material. You can create the pick HUs manually. When you confirm the warehouse task, you can manually assign the pick HUs to the warehouse task.

For more information about packing, see Packing During Warehouse Task Confirmation [Seite 511].

SAP Extended Warehouse Management (SAP EWM)

510

323

SAP Online Help

20.07.2007

Warehouse Task Item Split for Pick HUs If you determine during picking of the warehouse task items that the pick HU is too small for the entire item quantity, you can split the warehouse task item and pick in a newly-created pick HU, in other words, you can execute a partial picking.

Activities ●

If you want EWM to automatically create and assign the pick HUs, then in Customizing for EWM, choose Cross-Process Settings → Warehouse Order → Define Packing Profile for Warehouse Order Creation. ○

Define a packing profile.

○

If you want EWM to automatically create pick HUs, select Create HUs.

○

If you want EWM to automatically assign pick HUs to the warehouse tasks in the warehouse order, choose Assign HUs to WTs.

●

If you want EWM to automatically propose the number of pick HUs with the required packaging material, then in Customizing for EWM, choose Cross-Process Settings → Warehouse Order → Define Packing Profile for Warehouse Order Creation, and define a packing profile without choosing Create HUs or Assign HUs to WTs.

●

If you want to manually create and assign pick HUs, you do not define a packing profile in Customizing for EWM.

For more information about the packing profile, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Warehouse Order → Define Packing Profile for Warehouse Order Creation.

SAP Extended Warehouse Management (SAP EWM)

510

324

SAP Online Help

20.07.2007

Partial Picking Use In a partial picking, Extended Warehouse Management (EWM) can create a corresponding warehouse task for an outbound delivery, even though it cannot completely fill all items for the outbound delivery.

By default, EWM executes a partial picking. If the available quantity in the warehouse is not sufficient to fill all items of the outbound delivery, you can prevent the creation of a warehouse task.

Prerequisites If you want to execute a complete picking, you need to have made the settings for complete picking for warehouse order, in Customizing for Extended Warehouse Management (EWM) under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type.

Features You use the standard setting (partial picking) so that EWM creates a warehouse task even though it cannot completely fill all items of the outbound delivery. You use the complete picking, ●

so that EWM does not create a warehouse task during a background processing, such as wave release or processing using a Post Processing Framework action (PPF action).

●

so that EWM warns you in the user interface for warehouse task creation for warehouse requests, that the required quantity is underfilled and that a complete picking is required. You can cancel the warehouse task creation or save the warehouse task created internally.

You have created an outbound delivery with two products of 50 pieces each. Since creation of the outbound delivery, you have taken from the warehouse 10 pieces from the product in the second outbound delivery item, so that only 40 pieces remain. If you create a warehouse task for this outbound delivery, EWM notifies you that it cannot completely fill the picking requirements.

Activities The following table provides an overview of the possibilities within partial picking. Partial picking is allowed

Procedure

Results

EWM automatically adjusts the outbound delivery quantity to the warehouse task quantity.

In Customizing for Extended Warehouse Management, choose Cross-Process Settings → Exception Handling → Define Exception Codes and then Delivery Adjustment in Case of

EWM transfers the warehouse task quantity as warehouse request quantity to the corresponding items of the warehouse request.

SAP Extended Warehouse Management (SAP EWM)

510

325

SAP Online Help

20.07.2007 Differences. Define the delivery adjustment in the case of differences.

You manually adjust the outbound delivery quantity to the picked quantity.

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

EWM transfers the warehouse task quantity as warehouse request quantity to the corresponding item of the warehouse request.

Choose Change Mode and then Adjust Delivery Quantity. Adjust the outbound delivery quantity to the warehouse task quantity. Neither you nor EWM adjust the outbound delivery quantity to the picked quantity.

SAP Extended Warehouse Management (SAP EWM)

EWM has not yet completely picked the outbound delivery. You can create additional warehouse tasks so that EWM can fill all items of the outbound delivery.

510

326

SAP Online Help

20.07.2007

Pick Denial Purpose If Extended Warehouse Management (EWM) creates a warehouse task with reference to a warehouse request for an outbound delivery order, it is possible that EWM cannot create a new warehouse task, or can only create a warehouse task with a partial quantity. This is caused by one of the following reasons: ●

You have performed a storage bin denial.

●

EWM cannot find any, or not enough, stock to fulfill the requested quantity of the warehouse request.

In these cases there is a pick denial.

Prerequisites ●

For the case that EWM cannot completely fulfill the requested quantity of the warehouse request, you have not specified that warehouse task creation should be canceled. This means that the Business Add-In (BAdI) for the outbound delivery (/SCWM/TO_CREATE) does not use the method ABORT to cancel warehouse task creation. For more information, see the Implementation Guide (IMG) for EWM under Business Add-Ins (BAdIs) for Extended Warehouse Management → Cross-Process Settings → Warehouse Task → BAdI: WT Creation.

●

In Customizing, you have activated pick denial at warehouse number level. For more information, see the IMG for EWM under Goods Issue Process → Pick Denial → Activate Pick Denial at Warehouse Number Level.

●

In Customizing, you have activated pick denial at warehouse process type level. For more information, see the IMG for EWM under Goods Issue Process → Pick Denial → Activate Pick Denial at Warehouse Process Type Level.

●

You have defined your own exception codes for calling exception handling, and have assigned these to the internal exception codes defined by SAP. For more information, see the IMG for EWM under Cross-Process Settings → Exception Handling → Define Exception Codes and under Goods Receipt Process → Pick Denial → Assign Internal Exception Codes to Exception Codes.

Process ...

1. You or EWM want to create a warehouse task. However, EWM cannot create a new warehouse task, or can only create a warehouse task with a partial quantity. You can create a warehouse task using the user interface for stock removals for the outbound delivery order (online mode) or as a background job (background mode). You can start a background job, for example, using a Post Processing Framework action or a wave release. 2. EWM compares the requested quantity with the warehouse task quantity. If the system determines differences, it performs exception handling according to your Customizing settings. If you have specified an action in Customizing, for example, adjust the quantity in the warehouse request to the picked quantity, EWM triggers an alert and creates a workflow task. You or EWM perform the following:

SAP Extended Warehouse Management (SAP EWM)

510

327

SAP Online Help ○

20.07.2007

If you create the warehouse task in online mode, EWM displays a warning, depending on your Customizing settings, informing you that a pick denial has occurred. You can proceed as follows: ■

Confirm the action suggested by your Customizing settings by choosing Save . EWM executes a pick denial and executes a workflow in the background.

■

Change the action suggested by your Customizing settings and then choose Save . EWM executes a pick denial and executes a workflow in the background.

■

○

Execute the workflow using the action proposed by the system suggested by your Customizing settings, by choosing SAP Office → Folders → Inbox, or delete it and create a new warehouse task, for example if you still have stock in another storage type.

If EWM creates the warehouse task in background mode, it triggers a pick denial according to your Customizing settings, and performs any follow-up activity in the background. If you use wave management, EWM also writes an entry into the wave management log, informing you that EWM could not create a warehouse task, or could only create a warehouse task with a partial quantity.

3. Depending on your Customizing settings, EWM sends a message to ERP about the pick denial.

EWM does not send a message to ERP for a direct outbound delivery order. EWM only adjusts the outbound delivery quantity for the direct outbound delivery order.

Result Depending on your Customizing settings, EWM has executed the action for pick denial in the background. ●

The system did not execute an action.

●

The system adjusted the quantity in the warehouse request to the picked quantity, and sent a message about the pick denial to ERP if required.

For more information about reporting a change to an outbound delivery, see Processing of Outbound Deliveries [Seite 253] under “Notification of an outbound delivery change to the ERP system.“

SAP Extended Warehouse Management (SAP EWM)

510

328

SAP Online Help

20.07.2007

Cancellation of Picking Use If you have picked too much, for example, or if you require previously picked stock more urgently for another outbound delivery, you can cancel an outbound delivery either partially or completely.

Prerequisites If you want to release stock and simultaneously create a warehouse task (WT) in the background, you need to have performed the following in the Customizing settings for Extended Warehouse Management (EWM): ●

You have defined the warehouse process type for the cancellation of picking. For more information, see the Implementation Guide (IMG) for EWM under Goods Issue Process → Cancel Picking → Define Warehouse Process Type for Putback.

●

You have defined the warehouse process type for the cancellation of picking as a default value. For more information, see the IMG for EWM under Goods Issue Process → Cancel Picking → Define Warehouse Number Control for Putback.

Features EWM cancels previously picked stock of warehouse request items (WR items) or handling units (HUs), as well as reserved stock of WTs. EWM releases the assignment of picked or reserved stock from the WR items, HUs or WTs. This makes the stock freely available again. For packed stock, EWM can only release stock for the highest-level HU. In addition, EWM can only release stock for complete HUs. If EWM releases the assignment of a stock, the system can also create a new WT at the same time. If EWM is creating the WT in the foreground, the system proceeds as follows: ...

1. EWM starts by releasing the stock. 2. If the stock is unpacked, EWM then calls the transaction for moving products. If the stock is packed, EWM calls the transaction for moving HUs. 3. You define the new WT by creating storage bins or the warehouse process type for the new WT, for example. If EWM is creating the WT in the background, the system releases the stock and simultaneously creates a new WT with the specified warehouse process type. ...

On the Warehouse Request Items tab page, EWM gives you information that is relevant for the cancellation of picking for the WR item. On the Stock tab page, EWM gives you information about the stock, such as where the different stock is located in the warehouse. On the Open Product WT tab page, EWM displays the open product WTs of the WR items.

Activities Release Stock From One or More WR Items You can cancel stock that has already been picked for one or more WR items. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Cancel Picking. In the Document Number field for the search, you enter the outbound delivery that contains the WR item that you want to cancel. EWM shows you all WR items that belong to this outbound delivery. You can choose between the following options: ...

SAP Extended Warehouse Management (SAP EWM)

510

329

SAP Online Help

20.07.2007

●

You can release the entire picked delivery quantity for a WR item. To do this, on the Warehouse Request Items tab page you select the WR item that you want to cancel, and then choose Release Stock.

●

You can cancel the picked delivery quantity of a selected stock in the WR item only. To do this, on the Warehouse Request Items tab page, select the WR item that contains the corresponding stock. On the Stock tab page you then select the stock that you want to cancel, and then choose Release Stock.

●

You can cancel a partial quantity of the picked delivery quantity of a selected stock in the WR item only. To do this, on the Warehouse Request Items tab page, select the WR item that contains the corresponding stock. In the Cancel Quantity field on the Stock tab page, you then specify the delivery quantity that is to be cancelled for this stock. If you are working with serial number requirement Serial Numbers in Inventory Management [Seite 585], you can do the following: ○

You first specify the delivery quantity to be cancelled in the Cancel Quantity field and then choose Serial Numbers. EWM displays the serial numbers corresponding to the cancel quantity. You select the serial numbers that you want to cancel.

○

You start by choosing Serial Numbers. EWM displays all the serial numbers for the selected stock. You select the serial numbers that you want to cancel. EWM automatically calculates the delivery quantity that you have to cancel, and displays it in the Cancel Quantity field.

Release Stock From One or More HUs You can cancel stock that has already been picked for one or more HUs. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Cancel Picking. In the Handling Unit Identification field for the search, you enter the HU that you want to cancel. ●

You can release the entire picked delivery quantity for an HU. To do this, on the Handling Unit tab page you select the HU that you want to cancel, and then choose Release Stock. If you have packed multiple stocks into an HU, EWM displays the corresponding information on the Stock tab page. However, you cannot edit this data.

●

If you want to cancel a partial quantity of an HU only, you first have to repack the HU. To do this, on the Handling Unit tab page choose Repack HU (see Packing in the Work Center [Seite 506]).

Cancel WTs From One or More WR Items You can cancel stock that has already been reserved for one or more WTs. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Cancel Picking. In the Document Number field for the search, you enter the outbound delivery that contains the WR item whose WT you want to cancel. EWM shows you all WR items that belong to this outbound delivery. You can choose between the following options: ...

●

You can cancel the entire reserved delivery quantity for a WR item. To do this, on the Warehouse Request Items tab page you select the WR item whose WTs you want to cancel, and then choose Cancel WT. EWM then cancels all WTs that belong to the selected WR item.

●

You can cancel the reserved delivery quantity of a selected WT in the WR item only. To do this, on the Warehouse Request Items tab page, select the WR item that contains the corresponding WT. On the Open Product WT tab page you then select

SAP Extended Warehouse Management (SAP EWM)

510

330

SAP Online Help

20.07.2007

the WT that you want to cancel, and then choose Cancel WT. EWM then cancels the selected WTs only.

Cancel WTs From One or More HUs You can cancel stock that has already been reserved for one or more HUs. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Cancel Picking. In the Handling Unit Identification field for the search, you enter the HU that you want to cancel. On the Handling Unit tab page, you choose the corresponding HUs and then choose Cancel WT. EWM then cancels all open WTs that belong to these HUs.

Release Stock and Create WT Simultaneously (WR Item or HU) Corresponding to the above descriptions for releasing stock for WR items and HUs, EWM can simultaneously release stock and create new WTs (either in the foreground or in the background). To do this, follow the descriptions above for releasing stock. However, instead of choosing Release Stock, you choose Release Stock + Create WT.. You then select either Release Stock + WT in Foreground or Release Stock + WT in Background from the dropdown box.

SAP Extended Warehouse Management (SAP EWM)

510

331

SAP Online Help

20.07.2007

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

Prerequisites ●

The goods movement bin in the warehouse request from which you are booking out the stock for the goods issue must contain a valid storage bin in which a sufficient quantity of the product is available.

●

You use an item type that does not contain any of the following status types in the status profile: ○

Planned Picking

○

Picking

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

Process ...

1. You or EWM create the warehouse request for an outbound delivery order. Either ERP distributes an outbound delivery to EWM and EWM automatically generates a corresponding warehouse request, or you manually generate the warehouse request in EWM as a direct outbound delivery order [Seite 167]. You specify all the relevant stock attributes of the product (for example, the stock type) and a goods movement bin in the warehouse request. ○

If you have configured goods movement bin determination, EWM automatically suggests a goods movement bin. On the SAP Easy Access screen, choose Extended Warehouse Management → Settings → Maintain Goods Movement Bin Determination. EWM also uses the settings that you specify here to process inbound deliveries that are not relevant to putaway.

○

If you generate the warehouse request manually, choose one of the following options: ■

You specify the items with their stock attributes and quantities on the Items tab page.

■

On the HU tab page, you choose the Create and Save pushbuttons and specify a handling unit (HU) and an item type. Then EWM automatically creates the corresponding items with their stock attributes and quantities.

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

SAP Extended Warehouse Management (SAP EWM)

510

332

SAP Online Help

20.07.2007

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

SAP Extended Warehouse Management (SAP EWM)

510

333

SAP Online Help

20.07.2007

Storage Control Use You can use the process-oriented as well as layout-oriented methods for storage control. The goal of storage control is to display your complex putaway or stock removal process steps based on your processes or your layout data. During putaway or stock removal, an individual process step can be executed on single level basis or on multi level basis (that is, through intermediate storage types). You can combine the process-oriented storage control with the layout-oriented storage control. Here, EWM always executes the process-oriented storage control first. The layoutoriented storage control then checks whether the sequence of putaway process steps is possible in layout view, and if required, adjusts the flow of the putaway or stock removal.

Based on the process-oriented storage control, EWM determined the following putaway process flow: ●

Unloading at door

●

Counting at counting station

●

Checking the quality

●

Executing value-added services

●

Putaway in high rack storage area

The layout-oriented storage control determines that a direct putaway in the high rack storage area is not possible and that the putaway must occur with the use of an identification point. ●

Unloading at door

●

Counting at counting station

●

Identification of goods at the ID point [Extern]

●

Putaway in high rack storage area

Integration Extended Warehouse Managment (EWM) uses the delivery to determine, via delivery type and delivery item among others, the warehouse process type. This contains the procedure, in other words, the putaway or stock removal process with different activities. EWM transfers this operation to the handling unit to be put away or removed from stock. The handling unit thus contains the information concerning what process steps are required for the putaway or stock removal.

Prerequisites You have defined the following in Customizing for the putaway: ●

Paramaters that specify the work station determination for the next function (for example, counting) within the goods receipt process The following parameters are possible:

SAP Extended Warehouse Management (SAP EWM)

510

334

SAP Online Help

●

○

Source storage type

○

Destination activity area or destination storage type

○

Warehouse process type

○

Handling unit type

20.07.2007

Determination of the warehouse process type, using the delivery type and delivery item type, among others.

Features For information about the features of storage control, see Process-Oriented Storage Control [Seite 336] and Layout-Oriented Storage Control [Seite 340].

SAP Extended Warehouse Management (SAP EWM)

510

335

SAP Online Help

20.07.2007

Process-Oriented Storage Control Use You use this type of storage control to map complex putaways or stock removals. In doing so, you combine your storage process steps into one storage process. You can also trace the status of the individual process steps.

Process-oriented storage control only operates with handling units.

Integration For more information about integration, see Storage Control [Seite 334].

Prerequisites For more information about the prerequisites, see Storage Control [Seite 334].

Features You define the process steps for your complex storage process. A process step is, for example, unloading, counting, or deconsolidating [Seite 298]. Extended Warehouse Management (EWM) recognizes internal process steps predefined by SAP and external steps that you can define yourself. Your external process stesps can base themselves on internal ones. In addition, internal or external process steps can be simple, such as unloading, or combined, such as deconsolidating. For more information, see Direct and Combined Storage Control [Seite 268]. The process steps for the processes Counting and Deconsolidating predefined by SAP can be dynamic [Extern]. During goods receipt or goods issue, EWM copies the predefined process steps from the storage process type to the handling unit. EWM assigns these process steps to a handling unit as soon as it has created or changed them.

Activities For Customizing of process-oriented storage control, in the Implementation Guide (IMG) for EWM, choose Cross-Process Settings → Warehouse Task → Define Process-Oriented Storage Control.

SAP Extended Warehouse Management (SAP EWM)

510

336

SAP Online Help

20.07.2007

Direct and Combined Storage Control (Stock Removal) Use If you want to execute a direct stock removal, you do not have to define anything in the process-oriented storage control [Seite 336]. If you want to define complex stock removal processes, you have to use a combined processoriented storage control. Extended Warehouse Management (EWM) uses this during creation of a warehouse task to determine the intermediate storage types (for example, packing station). For information about integration and the prerequisites, see Storage Control [Seite 334] .

Features Direct Storage Control for Stock Removal If EWM determines that you are to pick a handling unit (HU) directly, it creates a warehouse task for this HU that determines the way from the source storage type to the destination storage type. For more information about updating the status, see Updating the Outbound Delivery Order in the GI Process [Seite 339]. The following graphic shows you the relationship between direct putaway and creation of warehouse tasks. Goods Issue Area

Source Storage Type 0010

Warehouse Task 1

Destination Storage Type 9020

Source Storage Type 0020

Warehouse Task 2

Destination Storage Type 9021

Combined Storage Control for Stock Removal If EWM determines that you are to pick a HU from stock using one or more intermediate storage types, it creates one warehouse task per route section for this HU. ●

One warehouse task that describes the route from source storage type to intermediate storage type

SAP Extended Warehouse Management (SAP EWM)

510

337

SAP Online Help

20.07.2007

Irrespective of your settings in Customizing, EWM also creates a warehouse task per product contained in the HU. ●

Based on your settings in Customizing, one warehouse task from the intermediate storage type to the next intermediate storage type, or to the final destination storage type.

You can carry out different activities at the intermediate storage types. For example, within a stock removal process, at an intermediate storage type, you can distribute HUs containing different products to stock removal HUs. In combined stock removal, you can determine the final destination storage type either right at the beginning of your stock removal process, or later. EWM manages the intermediate storage types in the same way as standard storage types. For example, you can break these down into storage sections and storage bins. For more information about updating the status, see Updating the Outbound Delivery Order in the GI Process [Seite 339]. The following graphic shows you the relationship between combined stock removal and creation of warehouse tasks.

Goods Issue Area

Intermediate Storage Type 8000

Source Storage Type 0010

Source Storage Type 0020

Warehouse Task 1.1

Intermediate Storage Type 8010

Warehouse Task 1.2

Intermediate Storage Type 8030

Warehouse Task 2.3

Destination Storage Type 9020

Warehouse Intermediate Task 2.1 Storage Type 8020

Warehouse Task 2.2

SAP Extended Warehouse Management (SAP EWM)

Destination Storage Type 9021

510

338

SAP Online Help

20.07.2007

Updating the Outbound Delivery Order in the GI Process Use Extended Warehouse Management (EWM) updates the outbound delivery order corresponding to the goods issue activities (GI activities).

Features EWM updates the outbound delivery order for the following GI processes: ●

Unpacked stock

You:

a. You or EWM generate the first product warehouse task (product WT). EWM sets the status Picking Planning in the outbound delivery order. b. You confirm the first product WT for picking. EWM sets the status Picking in the outbound delivery order. If the destination location in the product WT is a storage bin at the door or a transportation unit (TU), EWM sets the status Unloading in the outbound delivery order. ●

Packed stock

...

a. You or EWM generate the first product WT. EWM sets the status Picking Planning in the outbound delivery order. b. You confirm the first product WT for picking. EWM sets the status Picking in the outbound delivery order. c. You pack the stock. d. You or EWM generate the related loading warehouse task (loading WT), meaning the destination location corresponds to a bin at the door or to a TU. e. You confirm the loading WT. f. EWM sets the status Loading in the outbound delivery order.

SAP Extended Warehouse Management (SAP EWM)

510

339

SAP Online Help

20.07.2007

Layout-Oriented Storage Control Use You can use the layout-oriented storage control if stock movements in your warehouse do not travel from a source storage bin to a destination location directly, rather travel via intermediate storage bin.

The layout-oriented storage control only operates with handling units. One exception is the process display with picking or identification points. You use layout-oriented storage control in the material flow system [Seite 820] to define conveyor segments.

Integration For more information about integration, see Storage Control [Seite 334].

Prerequisites For more information about the prerequisites, see Storage Control [Seite 334].

Features For layout-oriented storage control, you define external warehouse process steps for your warehouse, including identification points [Extern] and pick points [Extern].

For example, you have a high rack storage area. If you want to move a product pallet from storage bin A (goods receiving area) to storage bin B (high rack storage area), the system should execute a contour and weight check to ensure that the product pallet can be put away in the high rack storage area safely. For this activity, Extended Warehouse Management (EWM) splits the warehouse order into two: one from storage bin A to identification point I, and a second from identification point I to storage bin B. You can move your goods using a pick point during picking.

Activities For Customizing of layout-oriented storage control, in the Implementation Guide (IMG) for EWM, choose Cross-Process Settings → Warehouse Task → Layout-Oriented Storage Control.

SAP Extended Warehouse Management (SAP EWM)

510

340

SAP Online Help

20.07.2007

Stock Determination Use You use stock determination to apply stock removal strategies during picking and stock transfers, based on predefined settings in Customizing. Based on the recorded product requirements, Extended Warehouse Management (EWM) determines in which sequence and from which storage types and stocks you should remove the desired product. EWM executes stock determination during creation of the warehouse task. In so doing, EWM takes into account own stocks, consignment stocks, and, in the case of internal movements, different stock types.

Prerequisites You have set stock determination groups in Customizing for EWM under Cross-Process Settings → Stock Determination → Maintain Stock Determination Groups, and have saved these groups in the master record so that EWM can execute stock determination for a product. You have made the settings in Customizing for EWM under Cross-Process Settings → Stock Determination → Set Stock Determination, for a stock determination strategy that the system uses to reduce stock. In so doing, you define a valuation to evaluate stocks of different owners or different stock types in a different manner.

For more information about Customizing for stock determination, see the Implementation Guide (IMG) for EWM under ●

Cross-Process Settings → Stock Determination → Maintain Stock Determination Groups

●

Cross-Process Settings → Stock Determination → Set Stock Determination

Features In EWM, stock determination occurs in the background during creation of warehouse tasks.

Stock Determination Strategies You can define the following stock determination strategies: Stock Determination Dominates During stock removal, EWM considers the warehouse number stock characteristics Owner and Stock Type as defined by you. In doing so, it uses the stock removal sequence to check the existing stocks for the corresponding stock. The stock removal sequence arises from prioritizing individual stocks according to the valuation you have defined. EWM first searches through existing stocks according to the stock characteristics that have the highest number of points. If the required stock is larger than the stock found, EWM searches the existing stocks according to the stock characteristics that have the next highest number of points. EWM continues this process until it finds enough stocks for the required stock, or it notifies you that it can only find a portion of the required stock.

SAP Extended Warehouse Management (SAP EWM)

510

341

SAP Online Help

20.07.2007

EWM Dominates During stock removal, EWM considers all allowed stocks, regardless of the stock characteristic of the warehouse number. It stores the required quantities and in so doing, only takes into account the stock removal rule defined in EWM, such as FIFO [Extern]. In this case, EWM removes the oldest quant from stock, irrespective of whether this is an own stock or a consignment stock. You can also use the stock determination’s number of points as sort criterion in the stock removal rule, so that for example, the stocks found per storage type are removed from stock according to descending number of points.

Activities In Customizing for EWM under Cross-Process Settings → Stock Determination → Maintain Stock Determination Groups, define the stock determination strategy (stock determination dominates or EWM dominates).

Example You define a stock determination strategy that you use during replenishment activities to firstly remove own stock (owner GLENN) and then to remove consignation stock for owner SCHMIDT (owner SCHMIDT). To do this, you define the following in Customizing for EWM: ●

Maintain stock determination group You define the stock determination group 01 for warehouse 001, using the stock determination strategy Stock Determination Dominates.

●

Set stock determination

Warehouse Number

Party Entitled to Dispose

Activity

Stock Determination Group

Current Number

Stock Ch

001

GLENN

Replenish ment

01

1

Owner

001

GLENN

Replenish ment

01

2

Owner

The system uses your stock determination strategy to search for the stock determination group 01. ●

If you have defined the strategy Stock Determination Dominates for the stock determination group 01, EWM first searches the warehouse for own stock according to the set stock removal strategy. If EWM cannot fill the required quantity for the warehouse task, it also searches for stocks from owner SCHMIDT and uses stocks found here as well, to fill the warehouse task’s required quantity.

●

If you have defined the strategy EWM Dominates for the stock determination group 01, EWM searches the warehouse for own stock and for stock from owner SCHMIDT, according to the set stock removal strategy. You define the stock removal sequence by using the storage type search sequence and the stock removal strategy, such as FIFO. You have made settings in Customizing for stock determination to define valuation points for the individual owners, and thus have undertaken a prioritization. You can use this prioritization to sort stocks for a storage type or storage type group.

SAP Extended Warehouse Management (SAP EWM)

510

342

SAP Online Help

20.07.2007

Storage Bin Determination for Stock Removal Use The aim of storage bin determination for stock removal is to determine storage bins and stock for stock removals and internal movements. Here, for example, the system uses parameters from the product master that you have defined manually or those that the system has determined in slotting [Seite 277]. You can define the business strategy according to which the storage bin determination for stock removal is to run, for example, FIFO (First In, First Out). You make the settings for these stock removal strategies [Seite 396] in Customizing. Storage bin determination for stock removal occurs automatically when warehouse tasks (WTs) are created.

Prerequisites ●

You have defined a stock removal rule in Customizing for Extended Warehouse Management (EWM) under Goods Issue Process → Strategies → Specify Stock Removal Rule.

●

You have defined a storage type search sequence in Customizing for EWM under Goods Issue Process → Strategies → Specify Storage Type Search Sequence.

●

You have assigned the storage type search sequence in Customizing for EWM under Goods Issue Process → Strategies → Determine Storage Type Search Sequence for Stock Removal.

●

You have assigned the stock removal rule to the storage type in Customizing for EWM under Master Data → Define Storage Type. Alternatively, you can assign the stock removal rule under Goods Issue Process → Strategies → Determine Storage Type Search Sequence for Stock Removal.

Features Determination of Stock Removal Search Sequence and Stock Removal Rule The stock removal search sequence contains information about the storage types in which the system is to search for stock and the order in which it is to sort the stock found. The stock removal rule specifies the order in which the system is to sort the individual quants. The system determines the stock removal search sequence on the basis of the parameters from the WT. In Customizing, you can link a stock removal rule to a stock removal search sequence. This means that the stock removal rule is fixed for all storage types belonging to the stock removal search sequence. If you have not linked the stock removal rule and the stock removal search sequence to one another, the system uses the stock removal rule that you have defined for the storage type or the storage type group. If you enter the storage type or the storage type group manually, the system calls the determination of stock removal search sequences to determine the stock removal rule. You can use the BAdIs in the /SCWM/ES_CORE_RMS enhancement spot to make changes to the result.

Determination of Storage Type or Storage Type Group The system uses the stock removal search sequence that was found to determine the storage type or the storage type group in which it is to search for stock.

SAP Extended Warehouse Management (SAP EWM)

510

343

SAP Online Help

20.07.2007

Selection of Quants The system uses the storage type or the storage type group that was found to select the stock. You can use the BAdIs in the /SCWM/ES_CORE_RMS enhancement spot to make changes to the result.

Sorting the Quants The system uses the stock removal rule that was found to sort the stock that was determined. You can use the BAdIs in the /SCWM/ES_CORE_RMS enhancement spot to make changes to the result.

Selection of a Quant The system chooses the first quant that was found, and checks it. If it cannot use this quant, for example, because the quantity is insufficient or the storage bin is locked for stock removal, the system takes the next quant, and so on.

SAP Extended Warehouse Management (SAP EWM)

510

344

SAP Online Help

20.07.2007

Work Center Determination in Goods Issue Use In Extended Warehouse Management (EWM), you can have the system determine a work center [Seite 35] in goods issue. You can specify various criteria for this determination.

Prerequisites In Customizing for EWM, you have set the Determine WkCtr indicator in the used warehouse order creation rule, under Extended Warehouse Management → Cross-Process Settings → Warehouse Order → Define Creation Rule for Warehouse Orders.

Features You can define the following criteria for the determination: ●

Warehouse number

●

Route

●

Activity area

●

Consolidation group

If you have set the indicator Determine WkCtr in the used warehouse order creation rule, EWM uses your criteria during warehouse order creation [Seite 419]. You can specify any number of criteria for the determination. EWM first attempts to find a work center matching your criteria. If it cannot find a work center, it uses the optimization that you have specified in Customizing for EWM under Extended Warehouse Management → Master Data → Work Center → Optimize Work Center Determination in Goods Issue. You also specify at least the storage bin for the work center determination. You can also specify the storage type or storage section. ●

If you specify the storage type or storage section, the storage type must have the storage type role Work center. If you only specify a storage type, this has to have the putaway rule Consolidation Group. EWM checks these settings when you save your details.

●

If you do not specify a storage type or storage section, EWM determines these values when you save your details.

Activities On the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Work Center → Determine Work Center in Goods Issue (/SCWM/PACKSTDT).

Result EWM analyzes the details that you enter here. EWM assigns the determined destination data storage type, storage section and storage bin to the warehouse tasks that it bundles using the warehouse order creation rule used here. This enables you to have the system determine a special work center for packing, depending on the route, for example.

SAP Extended Warehouse Management (SAP EWM)

510

345

SAP Online Help

20.07.2007

Replenishment Control Use You use replenishment control to fill up a picking area in accordance with the demand for products that you pick in this area. The data can come from the following sources: ●

Slotting [Seite 277]

Calculation of the minimum quantity [Extern] and the maximum quantity [Extern] as well as the minimum replenishment quantity [Extern] at storage type level or at fixed storage bin level ●

Open warehouse requests in accordance with selection

●

Manually entering the minimum and maximum quantity as well as the minimum replenishment quantity

Prerequisites ●

You have executed the following in Customizing under Extended Warehouse Management → Internal Warehouse Processes → Replenishment Control → Activate Replenishment Strategies in Storage Types: ○

You have activated the required replenishment strategy.

○

If you want to work with picker-directed replenishment, you have set the PckrDrvn Repl. indicator for direct replenishment and have, optionally, restricted storage types.

○

If the system is to automatically create a warehouse task when executing replenishment, you have set the WT Immed. indicator. Otherwise, the system creates a warehouse request or changes an existing warehouse request.

●

You have defined a stock removal control indicator for the warehouse number in Customizing under Extended Warehouse Management → Goods Issue Process → Strategies → Define Stock Removal Control Indicator.

●

You have defined tolerances and replenishment levels (fixed storage bin level or storage type level) in Customizing under Extended Warehouse Management → Master Data → Define Storage Type. You have also defined the following: ○

If you want to work with replenishment at storage type level, you have defined the minimum quantity and the maximum quantity in the warehouse product master.

○

If you want to work with replenishment at fixed storage bin level, you have defined fixed storage bins for your products as well as a minimum and a maximum quantity for each bin in the master data for Extended Warehouse Management under Storage Bin → Maintain Fixed Storage Bin.

If the system is to round replenishment quantities [Extern], you have defined a minimum replenishment quantity in the warehouse product master. You can only define the minimum replenishment quantity at storage type level, but the system can also use it at fixed storage bin level. ●

You have defined a default stock type for replenishment in Customizing under Extended Warehouse Management → Master Data → Define Warehouse Number Control.

SAP Extended Warehouse Management (SAP EWM)

510

346

SAP Online Help

20.07.2007

Features The following types of replenishment control are available: Planned replenishment You can start planned replenishment either interactively or in the background. The system calculates the replenishment in accordance with the defined minimum quantity and maximum quantity. Replenishment control is triggered when the stock is less than the minimum quantity. The system rounds down the replenishment quantity, in other words, the quantity of the warehouse task or the warehouse request, to a multiple of the minimum replenishment quantity. Order-related replenishment You can start order-related replenishment either interactively or in the background. The system calculates the replenishment in accordance with the quantity of the selected open warehouse requests. Replenishment control is triggered when the stock is less than the required quantity. The system rounds up the replenishment quantity to a multiple of the minimum replenishment quantity. The maximum quantity can be exceeded. Automatic replenishment The system starts automatic replenishment in the background when you confirm a warehouse task. It calculates the replenishment in accordance with the maximum and minimum quantity. Replenishment control is triggered when the stock is less than the minimum quantity. The system rounds down the replenishment quantity to a multiple of the minimum replenishment quantity. Direct replenishment Direct replenishment is only possible in fixed storage bin scenarios. It is started during a bin denial when an exception code refers to the internal process code Replenishment. The system calculates the replenishment in accordance with the maximum and minimum quantity. Here it assumes that the quantity at the storage bin is zero. The system rounds down the replenishment quantity to a multiple of the minimum replenishment quantity. Direct replenishment can be performed by the picker (picker-directed replenishment). In this case, a warehouse task is displayed for the replenishment as the next item to be processed in the picker’s warehouse order. As a prerequisite, the system must have found stock in the permitted storage types. Picker-directed replenishment is only possible in radio frequency scenarios.

We recommend that you use picker-directed replenishment if the reserve storage area is situated close to the picking area.

Activities To start planned replenishment or order-related replenishment, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Schedule Replenishment.

SAP Extended Warehouse Management (SAP EWM)

510

347

SAP Online Help

20.07.2007

Handling Differences When Picking for Warehouse Request Purpose When you confirm a warehouse task, differences between the product quantity requested and the product quantity available may result.

According to the warehouse task for a warehouse request, you are to pick 50 pieces of the product PROD-01 from the storage bin 02-03-44. However, you find only 45 pieces of the product in the storage bin. You confirm the warehouse task with a difference of 5 pieces.

Process ...

1. You want to remove a product from stock. 2. You pick a quantity smaller than the quantity specified on the corresponding warehouse task. 3. You record the quantity difference in the warehouse task by entering the quantity you have actually picked. 4. You confirm the warehouse task difference. 5. EWM updates the quantity to be picked in the warehouse request. 6. You decide how to proceed: ○

○

You want to conduct another picking for the warehouse request. ■

You create a further warehouse task for the warehouse request.

■

After you have confirmed the further warehouse task for the warehouse request, the picking for the warehouse request is closed completely.

You do not want to conduct a further picking for the warehouse request. EWM uses Adjust Delivery Quantity to equate the delivery quantity with the picked quantity. Through this adjustment, the pick status changes from Partially Completed to Completed. You can post the delivery for goods issue.

Results The warehouse request is completely picked. You can post the goods issue for the warehouse request.

SAP Extended Warehouse Management (SAP EWM)

510

348

SAP Online Help

20.07.2007

Kit to Order Purpose With this process, you can have the system automatically assemble kits to order if there is no kit [Extern] in stock. The following rules apply to kits: ●

A kit is always delivered in full to a customer.

●

The kit header and the kit components are always scheduled for the same date.

●

All components of a kit must come from the same warehouse (this can be achieved by means of internal transfer between warehouses).

●

Kit prices are always calculated at kit header level.

●

The kit header and kit component have a quantity ratio – defined by the kit structure – to each other. This quantity ratio is recalculated as soon as there are changes at kit header level or at kit component level.

If the kit is in stock, the SPM goods issue process takes place. For more information about the SPM Goods Issue Process, see the SAP Library for SAP ECC under Logistics → Logistics - General (LO) → SAP Service Parts Management (LO-SPM) → Goods Issue Process.

Prerequisites You are using the following systems: ●

SAP CRM 5.0 For more information, see the SAP Library for mySAP Customer Relationship Management under Components and Functions → Availability Check → Availability Check using SAP APO → Additional ATP Functions in Service Parts Management → Kits in the Sales Order.

●

SAP ECC 6.0 For more information about the required Customizing settings, see the SAP Library for SAP ECC under Logistics → Logistics - General (LO) → SAP Service Parts Management (SPM) → Goods Issue Process → Kit to Order → Customizing Settings.

●

SAP SCM 5.0 ○

Extended Warehouse Management (EWM): For more information about the required Customizing settings, see the Implementation Guide (IMG) for SCM under Extended Warehouse Management → Goods Issue Process → Make Settings for Kitting.

○

Advanced Planning and Optimization (APO): For more information, see Availability Check for Kits [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

349

SAP Online Help

20.07.2007

Process

...

1. You create a sales order (SAP CRM) a. The system triggers the rule-based ATP check in SAP SCM for a requirement from the sales order. The system determines one or more rules with substitutions. One of the substitutions is a kit. b. A requirement for a kit originates as an input product from the sales order. The system then triggers the ATP check in SAP SCM. c. The system initiates the credit check in SAP ECC. d. The system performs the price determination and checks for the sales order, as well as checks for foreign trade determination. e. The system transfers the data from the sales order to SAP ECC. For more information about editing sales orders, see the SAP Library for mySAP Customer Relationship Management under Components and Functions → Process Sales Orders. 2. The system performs an ATP check and confirms quantities (SAP SCM-APO) The system checks whether the kit is in stock. If the kit is not in stock, the production that is activated in the validation rule creates a kit structure that contains the kit components that the system requires to assemble the kit. The system then performs the ATP check for the kit components and confirms the quantities for the sales order. 3. The system creates an unchecked delivery (SAP ECC-SPM) without creating an order. For more information, see the SAP Library for SAP ECC under Logistics → Logistics General (LO) → SAP Service Parts Management (SPM) → Goods Issue Process → Creation and Update of Unchecked Deliveries.

SAP Extended Warehouse Management (SAP EWM)

510

350

SAP Online Help

20.07.2007

4. You convert the unchecked delivery to a checked delivery (SAP ECC-SPM). For more information, see the SAP Library for SAP ECC under Logistics → Logistics General (LO) → SAP Service Parts Management (SPM) → Goods Issue Process → Conversion of Unchecked to Checked Deliveries. 5. The system performs another ATP check for the various kit components and confirms the quantities from the checked delivery (SAP SCM-APO) For more information, see Availability Check for Kits [Extern]. 6. EWM creates a warehouse request for the outbound delivery (SAP SCM-EWM). When it receives notification from SAP ECC, EWM uses the checked delivery to automatically create an outbound delivery order, that is, a warehouse request for an outbound delivery. For more information, see Creation of a Warehouse Request for an Outbound Delivery Order [Seite 116]. 7. You pick the outbound delivery order (SAP SCM-EWM). For more information, see Creation of a Warehouse Request for an Outbound Delivery Order [Seite 116]. 8. The system changes/confirms the outbound delivery (SAP ECC-SPM) ○

The system changes the delivery if quantity shortages are reported by EWM and then confirms the delivery.

○

The system confirms the delivery if exact delivery fulfillment is reported by EWM.

For more information, see the SAP Library for SAP ECC under Logistics → Logistics General (LO) → SAP Service Parts Management (SPM) → Goods Issue Process → Processing of Checked Deliveries. 9. The system posts the goods issue for the kits (SAP ECC-SPM). For more information about posting goods issue, see the SAP Library for SAP ECC under Logistics → Logistics - General (LO) → SAP Service Parts Management (SPM) → Goods Issue Process → Transfer Posting for Kits. 10. The system clears ATP-confirmed quantities (SAP SCM-APO). 11. The system updates the stock (SAP SCM-APO). 12. The system updates the data in the sales order (SAP CRM). For more information about editing sales orders, see the SAP Library for mySAP Customer Relationship Management under Components and Functions → Process Sales Orders. 13. The system executes billing (SAP CRM).

SAP Extended Warehouse Management (SAP EWM)

510

351

SAP Online Help

20.07.2007

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

Use Extended Warehouse Management (EWM) does not save the kits as master data, instead it receives the information about the structure of a kit in the form of items of an outbound delivery from the ERP system (see also Kit in the Warehouse Request for the Outbound Delivery Order [Seite 234]). You can use the structure containing the kit in the outbound delivery in combination with a packaging specification as a basis for assembling or producing a kit in EWM.

Structure A kit can consist of the following levels: ●

Kit header

Kit component [Extern] ●

Replaced kit component [Extern] (optional)

EWM does not support nested kits, that is, kits in kits.

Integration EWM supports kits in the kit to order [Seite 349] process.

SAP Extended Warehouse Management (SAP EWM)

510

352

SAP Online Help

20.07.2007

Kitting at a Work Center with a VAS Order Purpose You can use this process to create a kit with a value-added service order [Seite 528] (VAS order). This provides you with the following VAS order options: ●

Working with a special kitting work center

●

Automatic determination of the kitting work center

Documentation about efforts and status tracking for kitting [Extern] ●

Integrating VAS processing into the delivery

You can use an indicator for the item type of the kit header to make the system generate an item for the kit header in the pick-handling unit (pick-HU). You can print out this HU item in a HU list, display it in the packing transaction, and confirm it to the ERP system. In EWM, a kitting instruction can exist in one of the following forms: ●

As free text from the SAP Customer Relationship Management sales order that forms the basis for the outbound delivery.

●

As free text that you have created in the warehouse request in EWM.

You can display this text in the work center as additional information.

Prerequisites You have made all the required settings for kitting in Customizing. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Make Settings for Kitting. An outbound delivery with kit items exists in EWM. You have created a packaging specification for the product of the kit header item as master data, so that you can create a VAS order. This packaging specification must have a level of the level type Kitting. If you are using process-oriented storage control, you must assign the corresponding warehouse process step (such as KIT) of the warehouse process used to the kitting level (see also: Process-Oriented Storage Control [Seite 336]).

Note that a packaging specification (and therefore a VAS order) can only have one level of the type Kitting. You can assign a packaging material to the kitting level as a proposal for packing the kit. If the system is to automatically generate an HU item for the kit header in the pick-HU, set the Create Kit Item indicator in Customizing. For more information about the packing profile, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Outbound Delivery → Define EWM-Specific Settings for Item Types.

Process ...

1. EWM receives an outbound delivery with kit component items from the ERP system. 2. Depending on your Customizing settings, either you manually create a VAS order or you have the system create one automatically (see also: VAS Order for the Kit Header Item of the Warehouse Reqeust [Seite 356]). 3. You generate warehouse tasks for the kit component items in EWM. 4. You pick the kit component into a pick-HU and confirm the warehouse tasks. The kit components are then at the kitting work center.

SAP Extended Warehouse Management (SAP EWM)

510

353

SAP Online Help

20.07.2007

○

If you have set the Create Kit Item indicator in Customizing and are working with pick-HUs, the system generates the kit header item in the pick-HU. You can then use these items in the work center to repack the entire kit into another HU.

○

If you have not set the Create Kit Item indicator in Customizing, you can generate the kit header item in the work center manually.

5. You assemble the kit in accordance with the kitting instructions where required. a. You can display the kitting instruction. b. You can report the work progress in the VAS order. 6. You pack the kit into an HU and generate the HU item for the kit header.

If the ERP system is dependent on an HU item for the confirmation, and you have not set the Create Kit Item indicator in Customizing, then you must generate the item manually after packing the kits in the work center at the latest. If a transfer posting of the stock from the kit components to the kit header takes place in the ERP system when processing the goods issue confirmation from EWM, the ERP system is dependent on this item (see also: Kit to Order [Seite 349]). 1. You generate an HU warehouse task to transport the HU to the goods issue zone. 2. You confirm the HU warehouse task. 3. You then post the goods issue for the warehouse request. If you have set the Create Kit Item indicator, the system uses this HU item in goods issue posting to check whether the packed kits are complete, meaning the system can therefore post these kits for goods issue.

The system only performs this check if the indicator is set in the item type of the kit header. This process allows you to use the following options: ●

Process-oriented storage control

●

Integrating the VAS order into storage control

●

Creating VAS orders based on a packaging specification

This enables you to provide additional steps in the warehouse process, such as loading. You can also define your own warehouse process steps for packing kits into an HU, such as in the following instances: ●

If you are not performing this step during kitting, but as an additional step at the same work center.

●

If you are packing the kits into an HU at a different work center after kitting.

The decision as to whether you map additional steps as a step in the warehouse process only, or as a level of the packaging specification as well, depends on whether you want to document this step in the VAS order. The system only generates a VAS activity where you can report effort and consumption of the packaging material if you have mapped this step as a level of the packaging specification.

Result You can ship the kit.

SAP Extended Warehouse Management (SAP EWM)

510

354

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

355

SAP Online Help

20.07.2007

VAS Order for the Kit Header Item of the Warehouse Request Purpose You can generate value-added service orders [Seite 528] (VAS orders) automatically or manually in Extended Warehouse Management (EWM), to document and monitor these value-added services. VAS orders that are generated for a kit header item have a special structure.

Prerequisites You have made the required settings in Customizing for generating VAS orders automatically or manually. If you want to create a VAS order for kit items in the delivery, make the settings for the item type of the kit header only. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Value-Added Services → Define Relevance for VAS Order. An outbound delivery with kit items exists in EWM. You have defined a packaging specification [Seite 494] with a level of type Kitting. Note that a packaging specification (and therefore a VAS order) can only have one level of the type Kitting.

Process Automatic Generation ...

1. You receive an outbound delivery with kit items from the ERP system. 2. EWM checks whether it is to generate a VAS order for the kit header item automatically, and generates it where appropriate. 3. EWM saves the number of the VAS order as a document flow for all kit items of the warehouse request. 4. If you have activated the VAS Order status in the status profile of the item type for the warehouse request item, EWM sets the VAS Order status of the kit items to one of the following entries: ○

Generated If you have defined in Customizing that EWM is to generate the VAS order automatically.

○

Not Relevant If you have defined in Customizing that EWM is not to generate the VAS order automatically.

Manual Generation ...

1. You receive an outbound delivery with kit items from the ERP system. 2. You create a VAS order for the kit header item manually (see also: Create and Edit VAS Orders [Seite 536]). 3. EWM creates the VAS order. When you save the VAS order, EWM saves the number of the VAS order as a document flow for all kit items of the warehouse request. 4. If you have activated the VAS Order status in the status profile of the item type for the warehouse request item, EWM sets the VAS Order status of the kit items to Generated.

SAP Extended Warehouse Management (SAP EWM)

510

356

SAP Online Help

20.07.2007

Result The system has created a VAS order for the kit header. You can use this VAS order for confirming services in the process Kitting at a Work Center with a VAS Order [Seite 353]. When you edit the VAS order, EWM changes the VAS Order status of the warehouse request item (see also: Updating the Warehouse Request Using the VAS Order [Seite 232]). The VAS order for the kit header has the following special features. For example, you have defined a packaging specification with the levels Oiling, Kitting, and Packing. The VAS order for the kit header has the following special features: ●

All activities prior to the kitting activity (such as oiling) and the kitting activity itself have kit component items of the delivery as their items. This is based on the assumption that you perform all activities prior to assembling the kits and the kitting activity itself in the kit components.

●

All activities after the kitting activity (such as packing) have the kit header item as their item. This is based on the assumption that you perform all activities after assembling the kits in the kit itself.

SAP Extended Warehouse Management (SAP EWM)

510

357

SAP Online Help

20.07.2007

Kitting at a Work Center Without a VAS Order Purpose You can use this process in Extended Warehouse Management (EWM) to create a kit without a value-added service order [Seite 528] (VAS order). Here you can configure a work center where you also pack in such a way that you can confirm generated kits there. This process is suitable for the following cases: ●

You do not require detailed documentation of the kitting procedure in EWM.

●

You are not performing kitting in one special kitting work center, but at a work center where you are also packing.

You can only find information about kitting in the information for the kit in the outbound delivery and in the kitting instruction that may exist in the form of free text for the warehouse request item of the kit. You can use an indicator for the item type of the kit header to make the system generate an item for the kit header in the pick-handling unit (pick-HU). You can print out this HU item in an HU list, display it in the packing transaction, and confirm it to the ERP system. In EWM, a kitting instruction can exist in one of the following forms: ●

As free text from the SAP Customer Relationship Management sales order that forms the basis for the outbound delivery.

●

As free text that you have created in the warehouse request in EWM.

You can display this text in the work center as additional information.

Prerequisites You have made all the required settings for kitting in Customizing. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Make Settings for Kitting. An outbound delivery with kit items exists in EWM. If the system is to automatically generate an HU item for the kit header in the pick-HU, set the Create Kit Item indicator in Customizing. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Outbound Delivery → Define EWM-Specific Settings for Item Types.

Process 1. EWM receives an outbound delivery with kit component items from the ERP system. 2. You generate warehouse tasks for the kit component items. 3. You pick the kit components into a pick-HU and confirm the warehouse tasks. The kit component items are then in the packing work center. ○

If you have set the Create Kit Item indicator in Customizing and are working with pick-HUs, the system generates the kit header item in the pick-HU. You can then repack these items into other HUs in the work center.

○

If you have not set the Create Kit Item indicator in Customizing, you can generate the kit header item in the work center manually.

4. You assemble the kit in the packing work center. 5. You pack the kit into an HU and generate the HU item for the kit header. 6. You generate an HU warehouse task to transport the HU to the goods issue zone.

SAP Extended Warehouse Management (SAP EWM)

510

358

SAP Online Help

20.07.2007

7. You confirm the HU warehouse task. 8. You then post the goods issue for the warehouse request. If you have set the Create Kit Item indicator, the system uses this HU item in goods issue posting to check whether the packed kits are complete, and therefore whether the system can post goods issue for these kits.

The system only performs this check if the indicator is set in the item type of the kit header. If the ERP system is dependent on an HU item for the confirmation, and you have not set the Create Kit Item indicator in Customizing, you must generate the item manually after packing the kits in the work center at the latest. If a transfer posting of the stock from the kit components to the kit header takes place in the ERP system when processing the goods issue confirmation from EWM, the ERP system is dependent on this item (see also: Kit to Order [Seite 349]). ...

Result You can ship the kit.

SAP Extended Warehouse Management (SAP EWM)

510

359

SAP Online Help

20.07.2007

Kitting During Picking Without a VAS Order Purpose You can use this process in Extended Warehouse Management (EWM) to create a kit during picking. This process is suitable for the following cases: ●

You do not require detailed documentation of the kitting procedure in EWM.

●

You assemble the kits during picking, that is, you do not perform kitting at special work centers.

You can only find information about kitting in the information for the kit in the outbound delivery and in the kitting instruction that may exist in the form of free text for the warehouse request item of the kit header. You can use an indicator for the item type of the kit header to make the system generate an item for the kit header in the pick-handling unit (pick-HU). You can print out this HU item in an HU list, display it in the packing transaction, and confirm it to the ERP system. In EWM, a kitting instruction can exist in one of the following forms: ●

As free text from the SAP Customer Relationship Management sales order that forms the basis for the outbound delivery.

●

As free text that you have created in the warehouse request in EWM.

You can display this text in the work center as additional information.

Prerequisites You have made all the required settings for kitting in Customizing. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Goods Issue Process → Make Settings for Kitting. An outbound delivery with kit items exists in EWM. If the system is to automatically generate an HU item for the kit header in the pick-HU, set the Create Kit Item indicator in Customizing. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Outbound Delivery → Define EWM-Specific Settings for Item Types.

If the ERP system is dependent on an HU item for the kit header in the confirmation of goods issue, you must make this setting. If a transfer posting of the stock from the kit components to the kit header takes place in the ERP system when processing the goods issue confirmation from EWM, the ERP system is dependent on this item (see also: Kit to Order [Seite 349]). ...

Process ...

1. EWM receives an outbound delivery with kit component items from the ERP system. 2. You generate warehouse tasks for the kit component items. 3. You pick the kit components and assemble the kit, where required in accordance with the kitting instruction. 4. You confirm the warehouse tasks.

SAP Extended Warehouse Management (SAP EWM)

510

360

SAP Online Help

20.07.2007

If you have set the Create Kit Item indicator in Customizing and are working with pickHUs, the system generates the kit header item in the pick-HU. You can then repack these items into other HUs in the work center. 5. You then post the goods issue for the warehouse request. If you have set the Create Kit Item indicator, the system uses this HU item in goods issue posting to check whether the packed kits are complete, and therefore whether the system can post goods issue for these kits.

The system only performs this check if the indicator is set in the item type of the kit header.

Results You can ship the kit.

SAP Extended Warehouse Management (SAP EWM)

510

361

SAP Online Help

20.07.2007

Packing at the Work Center Use Using packing in the work center, you can pack products into handling units (HU), and handling units into other handling units. For packing, there are various restriction options (filters) available for selection on the initial screen, for example, storage bin, handling unit, or delivery, which enable each user to optimize their worklist. On the left side of the work center screen, for example, you can use simple Drag&Drop to repack entire handling units, or to pack products into other handling units. The upper right screen area consists of tab pages that you can mainly use without a mouse. This transaction is particularly aimed at those users who physically pack products at work centers in the warehouse. The system supports entries using the keyboard or a scanner (where the necessary information is available as a bar code). You can also transmit the exact weight to the SAP system, using scales connected to the system, or you can print handling unit documents.

Prerequisites Ensure that you have made the required settings for packing in the work center, in Customizing and the SAP menu. For example, in the SAP menu you need to specify which storage bin is assigned to a work center. In Customizing, you specify which functions are executed at the relevant work center. The display for the different work centers is configurable. For example, in Customizing you can decide which of the available tab pages should be displayed for the user in the relevant work center. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management → Master Data → Work Center → Define Work Center Layout and Define Work Center.

Features Packing in the work center offers you the following range of functions: ●

Scanning of ○

HU Identification

○

Product

○

Warehouse Task

○

Storage Section

●

Creation of handling units

●

Repacking of handling units

●

Repacking of products

●

Post Differences

●

Changing handling units

●

Deconsolidation of handling units

You can configure packing in the work center in such a way that the system copies over frequently required data as default values for packing. In the Control area, you can make the following settings: ●

Standard storage bin

SAP Extended Warehouse Management (SAP EWM)

510

362

SAP Online Help

20.07.2007

●

Standard exception code

●

Propose Destination HU indicator

●

Propose Packaging Material indicator

●

External number assignment on/off

The display is divided into the left and right screen areas. You use the left screen area mainly for navigation, and for quick repacking of handling units and products (only using the mouse). In the right screen area, you can request various detailed information about the individual entries. The left screen area groups the display according to the following objects: ●

Storage section (displayed as

●

Storage bin (displayed as

●

Handling units (displayed as symbol

●

Storage section (displayed as

●

Open warehouse task (displayed as

symbol) symbol) or

, with or without system lock)

symbol) symbol)

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

SAP Extended Warehouse Management (SAP EWM)

510

363

SAP Online Help Quality inspections

o ●

20.07.2007

Warehouse Task ○

Possible destination HUs

Note that you edit and/or assign additional packaging materials in the Product area.

Functions for Objects In addition, you can execute the following functions from the right screen area: ●

●

●

Handling Units ○

Weigh

○

Close

○

Putback

○

Print

○

Delete

○

Empty

○

Aggregate

Product ○

Repack

○

Post Differences

Warehouse Task ○

Repack

○

Post Differences

Activities Since you can assign various work center categories to the work centers in Customizing, you also have the option of calling up the various work centers separately in the menu. The corresponding input help is then restricted, depending on the work center, to the data you have configured in Customizing. For more information, see the IMG under Define Work Center. ...

1. To access the various types of work center, choose one of the following menu paths: ...

a. From the SAP menu, choose Extended Warehouse Management → Execution → Packing - General b. From the SAP menu, choose Extended Warehouse Management → Execution → Quality Inspection and Count c. From the SAP menu, choose Extended Warehouse Management → Execution → Deconsolidation in Goods Receipt 2. Enter the relevant warehouse number, and use the input help to select the work center you require, if you have not assigned a work center to your terminal.

SAP Extended Warehouse Management (SAP EWM)

510

364

SAP Online Help

20.07.2007

You can assign a work center to your terminal in the system, so that during packing, the system automatically fills in the correct warehouse number and your work center. To do this, from the SAP menu choose Extended Warehouse Management → Master Data → Work Center → Define Master Data Attributes, and assign your terminal to the work center. You can also assign any scales that are connected to your work center.

Packing Using Drag and Drop In the area on the left, you can pack or unpack products in HUs, or pack HUs in other HUs as follows: ●

If you want to repack products in other HUs, select the product and drag it into another HU.

●

If you want to unpack products from other HUs, select the product and drag it to the storage bin.

●

If you want to pack an HU in another HU, select an HU and drag it into another HU.

Packing Partial Quantities Using Drag and Drop ...

1. If you want to repack just one partial quantity of a product, double click a higher-level node (HU or storage bin) in the area on the left. 2. Choose the tab page Contents in the area on the lower right. All the product items of the HU or storage bin are now visible. 3. Enter the quantity that you want to repack in the Partial Quantity field and choose Enter. 4. Drag the item from the area on the right into the target HU or target storage bin in which you want to repack these partial quantities. a. To do this, click any cell in this row that is not ready for input. b. Then use drag and drop to drag this cell to the target area (destination HU or destination storage bin).

SAP Extended Warehouse Management (SAP EWM)

510

365

SAP Online Help

20.07.2007

Scrapping Purpose In your warehouse you sometimes find products that are damaged, or that are unusable for some other reason. You often notice this, for example, during picking or physical inventory. Since you cannot normally sell these products on, you have to scrap them. You can use this process to create posting change notices for scrapping, and can remove these products from stock and post goods issue as usual.

Prerequisites ...

●

You have defined the following different document types for the posting change process, so that you can begin the scrapping process: ○

Document type for scrapping the entire quantity of a product

○

Document type for scrapping the entire quantity of a product except for a fixed remaining quantity

○

Document type for scrapping a partial quantity of a product

For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Internal Warehouse Processes → Delivery Processing → Posting Changes → Manual Settings → Define Document Types for Posting Change Process. ●

You have defined the warehouse process types for scrapping, in which you enter the work center for scrapping as the destination storage bin. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type.

●

You have defined the stock removal strategies for determining the stock to be scrapped. For more information, see the Implementation Guide (IMG) for Extended Warehouse Managements under Goods Receipt Process → Strategies.

●

You have defined the work center for scrapping, where you can pack the products to be scrapped together into a collection container. For more information, see the Implementation Guide (IMG) for Extended Warehouse Managements under Master Data → Work Center.

●

You have defined a non-picking-relevant document type and item type for the outbound delivery of the scrapping container. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Goods Issue Process → Outbound Delivery → Manual Settings → Define Document Types for the Outbound Delivery Process and Define Item Types for the Outbound Delivery Process.

Process ...

1. Create the posting change notice for scrapping. ...

a. For the entire quantity of a product b. For the entire quantity of a product except for a fixed remaining quantity

SAP Extended Warehouse Management (SAP EWM)

510

366

SAP Online Help

20.07.2007

c. For a partial quantity of a product (unsaleable or damaged products in the warehouse) 2. Create a warehouse task for scrapping with reference to the posting change notice 3. You can use a stock removal strategy to determine the stock to be scrapped. You can use different stock removal strategies for the entire quantity of a product and for the entire quantity of a product except for a fixed remaining quantity. 4. Remove the products to scrap from stock. You pick these products and confirm the warehouse tasks to the work center for scrapping. 5. You use the packing transaction to pack the products to scrap, and to construct handling units. 6. Use the handling units to create a non-picking-relevant outbound delivery. 7. Post the goods issue for the outbound delivery.

SAP Extended Warehouse Management (SAP EWM)

510

367

SAP Online Help

20.07.2007

Invoice Creation Before Goods Issue Use You can define when billing for SAP Customer Relationship Management (CRM billing) or billing for ERP (ERP billing) is to create an invoice for one single delivery or multiple deliveries. In the standard system, CRM billing or ERP billing creates the invoice after goods issue. However, if you require the invoice printout before the end of the loading and transportation process, such as for international transportation, you can create the current invoice before goods issue posting. You do this by sending an invoice request from Extended Warehouse Management (EWM) to CRM billing or ERP billing. You can request an invoice for each delivery or one or more invoices for the contents of a vehicle or transportation unit. ●

If you want to print invoices for the contents of a vehicle or transportation unit, EWM triggers the invoice printout in CRM billing or ERP billing by sending the message Print Billing Document.

●

If you want to create one invoice for each delivery, EWM triggers the creation and invoice printing automatically when it generates an outbound delivery.

Integration To be able to create and print invoices, you have performed the following: ●

If you are using CRM billing, you have connected an ERP and an SAP CRM system.

●

If you are using ERP billing, you have connected an ERP system.

EWM sends the invoice-relevant data to ERP. ERP copies the data to CRM billing or ERP billing. The following applies for invoice creation: ●

In the case of direct outbound delivery orders, the invoice is always created through ERP billing.

●

In the case of CRM orders, the invoice is always created through CRM billing.

●

In the case of ERP orders, the invoice is always created through ERP billing.

Prerequisites ●

If you are using CRM billing, you have set the IBGI (Invoicing Before Goods Issue) indicator in the data relevant to the business partner. You can override this indicator in the sales order. For more information, see the SAP Library under SAP CRM → Components and Functions → Sales → Sales Transaction → Sales Orders → Additional Functions for Service Parts Management.

●

If you are using ERP billing, you have set the IBGI (Invoicing Before Goods Issue) indicator in Customizing for ERP under Logistics Execution → Extended Warehouse Management Integration → Settings for Billing → Determine Invoicing Before Goods Issue.

●

You have defined specific characteristics in the route, such as the GTS geography group at header level, to determine whether a delivery must be checked by the customs authority. On the SAP Easy Access screen, choose Extended Warehouse

SAP Extended Warehouse Management (SAP EWM)

510

368

SAP Online Help

20.07.2007

Management → Master Data → Shipping and Receiving→ Transportation → Route Determination → Maintain Route. ●

You have determined that EWM requests CRM billing or ERP billing for single deliveries and also for groups of deliveries in accordance with the contents of a vehicle or a transportation unit. If, for example, a vehicle is carrying a delivery of 50 different regulators, EWM requests at least 50 invoices from CRM billing. In the SAP Easy Access screen, choose Extended Warehouse Management → Interfaces → Invoice Before Goods Issue.

●

In Customizing for EWM, you have defined the following for the document type and item type of the outbound delivery: ○

You have defined a process profile for the document type of the outbound delivery that allows invoicing before goods issue. For example, you are using document type OUTB Outbound Delivery Order with process profile /SCWM/OUT_PRD Outbound Delivery Order Standard for the delivery header, and process profile /SCWM/OUT_PRD_DLV Outbound Delivery Order Standard Item EWM for the delivery item. For more information, see IMG for EWM under Goods Issue Process → Outbound Delivery → Manual Settings → Define Document Types for Outbound Delivery Process. For more information about the individual process indicators, see the IMG for EWM under Cross-Process Settings → Delivery Processing → Process Profile for Delivery Document Header in the field help for the individual process indicator.

○

You have defined a process profile for the item types of the outbound delivery that allows invoicing before goods issue. For example, you use item type ODLV Standard Item Outbound Delivery with process profile /SCWM/OUT_PRD_DLV Outbound Delivery Order Standard Item. For more information, see the IMG for EWM under Cross-Process Settings → Delivery Processing → Process Control → Define Process Profile for Delivery Document Header or Define Process Profile for Delivery Document Item.

●

●

If you do not use routes in the outbound delivery, you can define the following in Customizing for EWM for the document type of the outbound delivery: ○

EWM triggers invoice creation and invoice printing automatically when it generates an outbound delivery

○

You trigger invoice creation and invoice printing manually on the user interface of the outbound delivery later

For the routes that you want to use in the invoice before goods issue process, you have defined one of the following options: ○

The invoice for the outbound deliveries is to be created individually

○

The invoice for the outbound deliveries is to be created as a group per transportation unit or per vehicle, or manually on the user interface for the outbound delivery.

In the SAP Easy Access screen, choose Extended Warehouse Management → Interfaces → Invoice Before Goods Issue.

Features For single requests from EWM, CRM billing or ERP billing directly creates single invoices that you cannot change. For changes, you have to delete the outbound delivery. This automatically cancels the invoice. If you then generate a new outbound delivery, the invoice is automatically created and printed again.

SAP Extended Warehouse Management (SAP EWM)

510

369

SAP Online Help

20.07.2007

For group requests from EWM, CRM billing or ERP billing creates one or more invoices for each vehicle or transportation unit. CRM billing creates corresponding billing due list items. ERP billing does not create any billing due list items. You can make changes to these deliveries in EWM. If these occur before invoice creation, ERP or SAP CRM updates its deliveries or the invoice-relevant data in accordance with the input from EWM. After you have posted the goods issue, you can only trigger the invoice printout from CRM billing or ERP billing. If more than one vehicle forwards the material for a sales order, you can create related outbound deliveries for each vehicle and request invoices for them.

Invoice Relevance With your settings at sales order level or delivery level, you can control the global relevance for invoice creation before goods issue at delivery item level. You can determine a print profile after CRM billing or ERP billing has selected the printer [Seite 372]. EWM finds the print profile and informs CRM billing or ERP billing accordingly. For printing single requests, the billing system uses the print profile found. For the printing of group requests, the billing system uses the profile of the first delivery that was found.

You must determine the same print profile in CRM billing or ERP billing and EWM, so that CRM billing or ERP billing can print invoices.

Invoice Cancellation You cannot change an invoice once it has been created. If, for example, you have loaded a handling unit on to a different transportation unit and want to change the invoice that has already been created, you have to perform an invoice cancellation. EWM sends the cancellation for the invoice that was created to CRM billing or ERP billing. You can then request invoice creation and invoice printing again for the changed shipment document or delivery.

Activities Among other things, SAP CRM determines whether EWM sends an invoice request for a delivery before the goods issue posting to CRM billing via ERP, due to the business partner status Invoice Creation Before Goods Issue Posting Allowed. You can override this setting in the sales order of SAP CRM. ERP uses the Customizing entries to determine whether the outbound delivery is relevant for the Invoice Before Goods Issue process. In ERP, you can configure for the sales document type and sales organization the indicator with which the document items are sent to EWM. If the IBGI indicator on the delivery item allows invoice before goods issue depending on the route, EWM decides which type of request it sends to CRM billing or ERP billing for invoice creation and invoice printing: ●

Single request for an immediate invoice creation and invoice printing

●

Group request for an invoice creation and invoice printing

If you want to request, print or cancel an invoice for a group request, on the SAP Easy Access screen, choose Extended Warehouse Management → Shipping and Receiving → Process Vehicle or Process Transportation Unit. If you are not using a vehicle or transportation unit in the outbound delivery, on the SAP Easy Access screen choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery or Pickup and then choose one of the following options: ●

Request Invoice EWM sends the message Create Invoice to SAP CRM or ERP.

SAP Extended Warehouse Management (SAP EWM)

510

370

SAP Online Help ●

20.07.2007

Cancel Invoice EWM sends the message Cancel Invoice to SAP CRM or ERP.

●

Print Invoice EWM sends the message Print Invoice to SAP CRM or ERP.

●

Get Status The system requests and displays the status of the invoice creation for the ERP delivery.

SAP Extended Warehouse Management (SAP EWM)

510

371

SAP Online Help

20.07.2007

Print Profile Determination for Invoice Printout Purpose You can use this process to define print profile determination for invoice creation before goods issue [Seite 368] in Extended Warehouse Management (EWM). Here, every goods issue area can have multiple printers for various document types, for example, for freight lists, bills of lading, or invoices. EWM always sends the print profile names for invoice printouts to ERP, irrespective of whether you print from ERP or from SAP Customer Relationship Management (SAP CRM).

Prerequisites ●

If appropriate, you have defined a print profile in the default values. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Pickup. Choose Default Values and enter a print profile.

●

If appropriate, you have implemented your own print profile determination in Business Add-In (BAdI) /SCWM/EX_DLV_PRINT_PROFILE. For more information, see the BAdI documentation.

●

If appropriate, you have defined one or more print profiles in Customizing for EWM. For more information, see the Implementation Guide (IMG) for EWM under Extended Warehouse Management → Goods Receipt Process → Inbound Delivery → Print → Define Print Profiles for Delivery Processing and Goods Issue Process → Outbound Delivery → Print → Define Print Profiles for Delivery Processing.

●

You have defined print profile determination for the goods receipt process or goods issue process in Customizing for EWM. For more information, see the IMG for EWM under Extended Warehouse Management → Goods Receipt Process → Inbound Delivery → Print → Define Print Profile Determination for Goods Receipt Process or Goods Issue Process → Outbound Delivery → Print → Define Print Profile Determination for Goods Issue Process.

Process EWM attempts to determine the print profile in the following sequence: ...

1. EWM checks whether you have specified a print profile in the default values on the user interface for pickup. If so, it uses the name of this print profile. 2. If EWM cannot find a print profile in step 1, it checks whether you have implemented your own print profile determination in BAdI /SCWM/EX_DLV_PRINT_PROFILE. EWM uses the name of this print profile. 3. If EWM cannot find a print profile in step 2, it checks whether you have defined a print profile determination for the goods receipt process or the goods issue process in Customizing for EWM. EWM uses the name of this print profile. You can define an access sequence for print profile determination. As a result, EWM considers one or more combinations of different parameters for the print profile, for example, goods receipt office, ship-to location, and warehouse number. If EWM cannot determine a print profile, it does not send a print profile name to ERP. If EWM requests a single print from CRM billing, CRM billing uses the print profile that EWM sends. EWM determines this print profile in the sequence described above.

SAP Extended Warehouse Management (SAP EWM)

510

372

SAP Online Help

20.07.2007

If EWM requests a grouped print for multiple deliveries from CRM billing, EWM always sends the first print profile that is found by delivery processing. For information about invoice relevance, the invoice printout, and invoice cancellation, see Invoice Creation Before Goods Issue [Seite 368].

If you want to synchronize invoice printing with delivery note printing, you must ensure that EWM determines the printer for delivery note printing using a print profile (see Printer Determination in Delivery Processing [Seite 141]). This is because EWM only sends the print profile name to ERP and not the printer name. See also: Printing Delivery Notes [Seite 143]

SAP Extended Warehouse Management (SAP EWM)

510

373

SAP Online Help

20.07.2007

Putaway and Stock Removal Strategies Use In Extended Warehouse Management (EWM), the system uses putaway strategies [Seite 375] and stock removal strategies [Seite 396] to determine storage bins and stock. Each time that a warehouse task (WT) is created, the system reverts to putaway and stock removal strategies. ●

Goods receipts The system uses putaway strategies and parameters defined in the product master to utilize the available warehouse capacity by automatically determining suitable storage bins for the new products.

●

Goods Issues The system uses stock removal strategies to determine the optimal picking bin. If you decide to manually process certain goods movements, you can change source and destination storage bins that are automatically proposed by the system.

●

Internal stock transfers The system uses putaway and stock removal strategies, for example, for rearrangement [Seite 287], posting changes, and replenishment control [Seite 346].

Prerequisites You make the settings for putaway and stock removal strategies in Customizing for EWM under Goods Receipt Process → Strategies or Goods Issue Process → Strategies. For more information, see the Implementation Guide (IMG) and the documentation for the individual strategies. See also: Storage Bin Determination for Putaway [Seite 291] Storage Bin Determination for Stock Removal [Seite 343]

SAP Extended Warehouse Management (SAP EWM)

510

374

SAP Online Help

20.07.2007

Putaway Strategies Use In Extended Warehouse Management (EWM), you use putaway strategies [Extern] to optimize the storage of products.

Prerequisites You make the settings for the putaway strategies in Customizing for Extended Warehouse Management (EWM) under Goods Receipt Process → Strategies. For more information, see the Implementation Guide (IMG) and the documentation for the individual strategies.

Features The following table shows possible putaway strategies: Strategy

Comment

Manual Entry [Seite 376]

The system uses the storage bin that you have entered.

Fixed Storage Bin [Seite 377]

The system searches for a fixed storage bin.

General Storage [Seite 379]

The system searches in the general storage area.

Addition to Existing Stock [Seite 380]

The system searches for a storage bin that already contains stock.

Empty Storage Bin [Seite 381]

The system searches for an empty storage bin.

Near Fixed Picking Bin [Seite 382]

The system searches for a storage bin in the reserve storage type near to the fixed picking bin of the picking storage type.

Pallet Storage (by HU Type) [Seite 383]

The system determines the storage bin on the basis of the handling unit type.

Bulk Storage [Seite 387]

The system searches for a storage bin in the bulk storage area.

You can use the BAdIs in the /SCWM/ES_CORE_PTS enhancement spot to make changes to these putaway strategies. See Also: Storage Bin Determination for Putaway [Seite 291]

SAP Extended Warehouse Management (SAP EWM)

510

375

SAP Online Help

20.07.2007

Manual Entry Use The system does not determine a storage section or a storage bin. You enter the destination storage bin manually when the warehouse task is created. You use this procedure if the search for a suitable storage bin is performed on-site by the warehouse worker. First the warehouse worker searches for the suitable storage bin. Then the system automatically determines the data using the storage bin (for example, the storage type) in the warehouse task.

We recommend that you manually enter the storage bin in the case of mixed storage and storage types with the role “Staging Area Group”. You can use manual entry in the following transactions: ●

Putaway for inbound delivery (/SCWM/TODLV_I)

●

Stock removal for outbound delivery order (/SCWM/TODLV_O)

●

Stock transfer for internal stock transfer (/SCWM/TODLV_M)

●

Stock transfer for posting change (/SCWM/TODLV_T)

●

Move handling unit (/SCWM/ADHU)

●

Move product (/SCWM/ADPROD)

Prerequisites You have made the following settings for the storage type in Customizing for Extended Warehouse Management (EWM) under Master Data → Define Storage Type: ●

You have chosen the Standard Warehouse value in the Storage Behavior field.

●

You have chosen the Empty Bin or Addition to Existing Stock/Empty Bin value in the Putaway Rules field.

●

You have chosen the Only Storage Type value in the WT Generic field.

SAP Extended Warehouse Management (SAP EWM)

510

376

SAP Online Help

20.07.2007

Strategy: Fixed Storage Bin Use You apply this strategy if you want to put away a product in fixed storage bins in a storage type. You use this strategy primarily in storage types from which picking is done manually. You assign fixed storage bins manually. If you want to put away a product without fixed bin assignment in a storage type for which you have defined the strategy “Fixed Storage Bin”, the system determines a suitable storage bin and assigns it to the product as a fixed storage bin. The following figure is an example of a fixed bin assignment. In this example, warehouse 0001 has several fixed storage bins: FIX-AA, FIX-BB, and FIX-DD. Multiple fixed storage bins can be available for a product, for example, FIX-1-BB and FIX-2-BB for product BB.

AA

B-B

FIX-AA

FIX-1-BB

FIX-1-DD

FIX-2-DD

FIX-2-BB

Warehouse No. 0001 Party Ent. to Disp. BP0001 Product AA Fixed Bin: Fix-AA

Prerequisites ●

You have defined fixed storage bins in the master data for Extended Warehouse Management (EWM) under Storage Bin → Maintain Fixed Storage Bin.

●

You have made the following settings for the storage type in Customizing for EWM under Master Data → Define Storage Type: ○

You have chosen the Standard Warehouse value in the Storage Behavior field.

○

You have chosen the Addition to Existing Stock/Empty Bin value in the Putaway Rules field.

○

You have set the Fixed Bins Allowed indicator.

○

You have defined a maximum number of fixed storage bins in the Max. Fixed Bins field (you can also make this setting in the product master).

○

You have chosen the Addition to existing stock permitted value in the Addn.Stock Forbidden field.

SAP Extended Warehouse Management (SAP EWM)

510

377

SAP Online Help ○

20.07.2007

You have chosen a method in the Capacity Check field to activate the capacity check.

SAP Extended Warehouse Management (SAP EWM)

510

378

SAP Online Help

20.07.2007

Strategy: General Storage Use The system uses this strategy to find a storage bin in a general storage area. General storage is a type of warehouse organization in which you define a single storage bin per storage section. The quants in the storage bin can also be in the form of mixed storage. For each storage type, you can define one or more general storage areas. The following figure illustrates general storage. Two general storage areas (bin XXX and bin YYY) are available with mixed storage in storage type 0005. This means that you can put away product F in bin XXX even though product X has already been put away there. Storage Type 0005 Y B

Product X Bin XXX

Bin YYY

Product F

Prerequisites You have made the following settings in Customizing for Extended Warehouse Management (EWM) under Master Data → Define Storage Type: ●

You have chosen the Standard Warehouse value in the Storage Behavior field.

●

You have chosen the General Storage Area value in the Putaway Rules field.

●

You have chosen the Mixed Storage Without Limitations value in the Mixed Storage field.

SAP Extended Warehouse Management (SAP EWM)

510

379

SAP Online Help

20.07.2007

Strategy: Addition to Existing Stock Use With this strategy, the system prefers to put away stock in storage bins that already contain stock of the relevant product. A prerequisite for addition to existing stock is that sufficient free capacity still exists in the relevant storage bin. If the system cannot find a storage bin with the same product or if the storage bin does not have sufficient free capacity to store additional quants, the system searches for the next empty storage bin. This strategy violates the FIFO principle. For this reason, you should only use this strategy in situations where you have insufficient space. The following figure shows an example of addition to existing stock. You want to put away product AA. Since AA is already occupying a storage bin and free capacity is still available, you can add the product to the existing stock.

BB

AA

AA

Prerequisites You have made the following settings for the storage type in Customizing for EWM under Master Data → Define Storage Type: ●

You have chosen the Standard Warehouse value in the Storage Behavior field.

●

You have chosen the Addition to Existing Stock/Empty Bin value in the Putaway Rules field.

●

You have specified in the Addn.Stock Forbidden field whether or not you want to allow additions to existing stock. If you want to allow additions to existing stock, choose “ ” (Addition to existing stock permitted) or “M” (Addition to existing stock via addtn ID in product master). If you choose “M”, you must choose the required value for the Addit.to Exist.Stock indicator in the product master.

●

You have chosen a method in the Capacity Check field to activate the capacity check.

●

You have chosen the value 3 in the Mixed Storage field (one HU allowed per bin, in other words, mixed storage is not permitted).

SAP Extended Warehouse Management (SAP EWM)

510

380

SAP Online Help

20.07.2007

Strategy: Empty Storage Bin Use With this strategy, the system proposes an empty storage bin. You can use this strategy to support warehouses that are organized randomly, where products are stored in individual storage sections. This strategy is especially suited for high rack storage and shelf storage.

Prerequisites You have made the following settings for the storage type in Customizing for Extended Warehouse Management (EWM) under Master Data → Define Storage Type: ●

You have chosen the Standard Warehouse value in the Storage Behavior field.

●

You have chosen the Empty Bin value in the Putaway Rules field.

●

Optionally, you can change the sort sequence of the storage bins that has an effect on the determination of the empty storage bin under SrchRule EmptyBin.

SAP Extended Warehouse Management (SAP EWM)

510

381

SAP Online Help

20.07.2007

Strategy: Near Fixed Picking Bin Use You use this strategy when you put away products in a reserve storage area. This strategy is intended for situations where reserve storage bins of a reserve storage type are located directly above the fixed storage bins in a picking storage type (nearby reserve). You can configure whether the system checks if a fixed storage bin is available. You can set up your system in such a way that it first searches for a fixed storage bin in a picking storage type. If it does not find an empty bin, it then uses the "Near Fixed Picking Bin” strategy to search for a bin in a reserve storage type that is as close as possible to the fixed storage bin of the product. The system first tries to find a reserve storage bin in the stack where the fixed storage bin is located. Here the system starts on the lowest level and works its way up. If it does not find an empty bin, it searches to the right of the fixed storage bin and then to the left in the same aisle, before searching in the adjoining aisles. Here it always searches from the bottom upwards. If multiple fixed storage bins are available for the product in the picking storage type, the system takes the first fixed storage bin that it finds as the starting point.

Prerequisites You have made the following settings for the storage type in Customizing for Extended Warehouse Management (EWM) under Master Data → Define Storage Type: ●

You have chosen the Standard Warehouse value in the Storage Behavior field.

●

You have chosen the Empty Bin value in the Putaway Rules field.

●

You have chosen the Near to Fixed Bin value in the SrchRule EmptyBin field.

●

You have given the storage bins in the picking storage type and the reserve storage type the same names.

SAP Extended Warehouse Management (SAP EWM)

510

382

SAP Online Help

20.07.2007

Strategy: Pallet Storage (by HU Type) Use Using this putaway strategy, the system processes different HU types (for example, pallets) and allocates them to a suitable storage bin section. One storage bin is often divided into several smaller sections. You can only put away the same HU types in a storage bin.

Explanation of the Strategy High rack storage is frequently designed so that a storage bin can accommodate several different HU types. The following figure shows the “Pallet Storage by HU Type” strategy. For example, a storage bin can accommodate multiple pallets depending on the size of the pallet, such as three europallets (80 x 120) or two industrial pallets (100 x 120). A storage bin may be able to accommodate a single oversized pallet or several very narrow pallets. 2

1 Bin Type PA

HU Type P2

Europallet

A Bin Type PA

3

02-10-01

B HU Type P1

Industrial Pallet 02-09-01 1

3

2

Bin Type PA 02-08-01 Industrial Pallet

With this strategy, you define the maximum number of quants for each combination of storage bin type and HU type. The first time that the system puts away products in this storage bin, it determines the storage bin sectioning that it assigns to the storage bin. The system also determines which and how many HUs it can put away in the storage bins.

Prerequisites You have made the following settings for the storage type in Customizing for EWM under Master Data → Define Storage Type: ●

You have chosen the Pallet Storage value in the Storage Behavior field.

●

You have chosen the Empty Bin value in the Putaway Rules field.

●

You have activated the HU type check.

●

You have chosen the Mixed Storage Without Limitations value in the Mixed Storage field.

SAP Extended Warehouse Management (SAP EWM)

510

383

SAP Online Help

20.07.2007

Definition of Storage Bin Sections The following table shows the number of storage bin sections that you can define for a storage bin. This means that you use this number to control the number of HUs that can occupy a storage bin.

Define Storage Bin Sections WNr

Type SecKey No. Bin Functional 1 Secs Location Category

2

0001

0007 A

2

BT01

A

B

0001

0007 B

3

BT01

1

2

3

4

5

6

.... (Bin Secs)

3

Section Key The storage bin sectioning determines which HU types and how many handling units (HUs) of each type you can put into a storage bin. The storage bin sectioning is determined dynamically on the basis of the first HU that you put away. The system deletes the storage bin sectioning as soon as you have removed the last HU from the storage bin.

Nomenclature of Storage Bin Sections To name each individual section of a storage bin, you enter either a one-digit or a two-digit suffix (for example, A1, BB, 12) in one of the columns numbered from 1 to 99 under the heading Sections. The system displays the total number of storage bin sections that you have defined in the Number of Sections field. The system attaches this suffix to the name of the storage bin and separates it with a slash (/). Note that the name of the storage bin sections is 2-3 digits longer than that of the main storage bins. Therefore, the length of the name of the main storage bin must be 2-3 digits shorter than the permitted length for the storage bin name.

The storage bin sections that you have defined for warehouse 0001 and storage type 0007 (shown in the following table) form the basis of the example. Assuming that the storage bin is named 02-10-01, the system identifies the three storage bin sections in the main storage bin as follows: 02-10-01/1 02-10-01/2

02-10-01/3

Once you have defined storage bin sections for a storage type, you cannot change them.

Assignment of Storage Bins and HU Types For each storage type, you assign the appropriate storage bin sectioning to each allowed combination of storage bin type (Storage Bin Type field) and HU type (HU Type field).

Assign Storage Bin Types and HU Types WNr

Type

BinTy

HU Type

SecKey

No. Bin Secs

0001

0007

PA

E1

B

3

0001

0007

PA

IP

A

2

SAP Extended Warehouse Management (SAP EWM)

510

384

SAP Online Help

20.07.2007

When you create storage bins for this strategy, you must specify a storage bin type. This storage bin type must match the storage bin type in the table for assigning storage bin types and HU types (see above). Once you have made these assignments, you cannot change them later. When you put away products into a storage type for which storage bin sectioning has been defined, you must enter the HU type in the preparation screen of the warehouse task. The system uses this HU type to search for suitable empty storage bins. At the same time, the system ensures that you put away only one HU type per storage bin.

Additional Option If you assign the same storage bin type and a different HU type to the same section key, you can also put away more than one pallet type into the same storage bin.

Assign Storage Bin Types and HU Types WNr

Type

BinTy

HU Type

SecKey

No. Bin Secs

0001

0007

PA

E1

B

3

0001

0007

PA

IP

A

2

0001

0007

PA

E2

A

2

If you define the table as shown above, you can place an industrial pallet (IP) into the first section of the storage bin and an HU with the type E2 into the second section of the storage bin.

SAP Extended Warehouse Management (SAP EWM)

510

385

SAP Online Help

20.07.2007

Example: Optional HU Check When Creating a WT The system can only find the appropriate storage bins for a handling unit type when creating warehouse tasks (WT) if you have activated the HU type check. You can enter *** as an allowed HU type in this table. This entry means that all the HU types in this storage type are allowed. The system then searches for a suitable storage bin for the HU type on the basis of the allowed storage bin types per HU type.

Before you activate the optional HU type check, you should check the table parameters carefully. If the configuration settings are not optimal, you may encounter performance problems. The following example outlines the performance problems associated with the optional HU type check and their solutions:

■

Storage bin types P1, P2, P3, P4, and P5 are allowed for HU type E1. The system is to put away HU type E1 in storage type 0001. However, only storage bins of the type P0 are available in this storage type.

■

The system is not allowed to put away HU type E1 in storage type 0001. A system that has been configured optimally recognizes this (since access to a completely buffered table is possible) and searches for a suitable storage bin in the next storage type.

■

In the optional HU type check, the system tries to access the database five times without success. If you work with different storage sections, this number increases accordingly.

You can easily check the Customizing settings by viewing the log for the storage bin search. The greater the number of unsuccessful attempts that the system has made, the more ineffective the process for storage bin determination becomes. You should reduce the number of attempts by optimizing the storage type search.

SAP Extended Warehouse Management (SAP EWM)

510

386

SAP Online Help

20.07.2007

Strategy: Bulk Storage Use Products such as tires, glass products, and drinks that come in large quantities and require a large amount of storage space are often stored in bulk storage. The advantages of bulk storage include: ●

Reduced need for physical storage bins

●

Fast access to the containers

●

Clear structuring of the warehouse (into blocks and rows)

This strategy searches for storage bins in bulk storage. The figure below shows bulk storage: HU Type E1

XX Row 02

Bin: A05-01 A05-02 Quant: XX XX HU Type: I1 E1

A05-03 A05-04 ZZ E1

The most important features of bulk storage processing are: ●

Freely-defined coordinate structure When you define the storage bins in bulk storage, you do not have to take any technical prerequisites of the system into account. The warehouse is divided into blocks, which in turn are divided into individual rows.

●

One storage bin per row In practice, a row is selected as the sort characteristic in bulk storage. In the system, a row is created and managed as a storage bin. The storage bins (rows) are classified according to storage bin types. For example, rows 2 and 3 in block A05 (illustrated in the above figure) can hold up to 16 pallets. However the 4th row can only hold a maximum of 12 pallets, due to a structural column in the row. You can enter this exception (reduced capacity of a row) when defining the block structure (see section “Prerequisites”).

●

Different HU types In bulk storage, you often manage different HU types with different dimensions, for example, standard pallets and industrial pallets with clip-on mounts. Extended Warehouse Management (EWM) supports the management of different HU types in bulk storage.

●

Mixed storage

SAP Extended Warehouse Management (SAP EWM)

510

387

SAP Online Help

20.07.2007

You do not put away HUs with different products in the same row. However, in general, all combinations of mixed storage are allowed in bulk storage. You can also define that all products in the storage bin must have the same batch. ●

Automatic blocking per row To optimize the putaway and stock removal processes in bulk storage, you can set a blocking indicator for each row separately.

Prerequisites ●

●

You have made the following settings for the storage type in Customizing for Extended Warehouse Management (EWM) under Master Data → Define Storage Type: ○

You have chosen the Bulk Storage value in the Storage Behavior field.

○

You have chosen the Addition to Existing Stock/Empty Bin value in the Putaway Rules field.

○

You have chosen the Addition to existing stock permitted value in the Addn.Stock Forbidden field.

○

Do not activate the HU type check and do not choose a capacity check method. A capacity check and HU type check are not necessary in bulk storage because an internal check is carried out based on the block structure definition.

○

Choose the required option in the Mixed Storage field. For more information about the permitted combinations, see the relevant field help.

When defining the storage type control for this strategy, you must take into consideration the following indicators, among others, to control the putaway of products into bulk storage: ○

Putaway blocking for row

○

Time limit for blocking

For more information about these control options, see the Implementation Guide (IMG) for EWM under Goods Receipt Process → Strategies → Putaway Rules → Putaway Behavior: Bulk Storage → Storage Type Control for Bulk Storage.

Definition of Bulk Storage Indicators For this strategy, you can enter bulk storage indicators together with a description. Using the bulk storage indicator, you define how you want to store a particular product in bulk storage. To do this, you enter the bulk storage indicator in the product master record and again in the bulk storage sectioning table when defining the structure of a block.

Block Structure Definition You can define various characteristics of bulk storage such as storage bin types, HU types, maximum number of stacks, and stacking height. When you define storage bins for bulk storage you must enter a storage bin type.

Other Control Options In the product master record (in the Warehouse Management view), you can ●

Define up to three HU types

●

Set the bulk storage indicator

●

Set the indicator allowing addition to existing stock

SAP Extended Warehouse Management (SAP EWM)

510

388

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

389

SAP Online Help

20.07.2007

Cross-Line Stock Putaway Use In the case of this function, a sort sequence supports the system when searching for suitable storage bins. You can use sort sequences to prevent one part of the warehouse from being overburdened and to optimize the putaway of goods. If you have not defined a sort sequence, the system sorts by storage bin name.

We recommend cross-line stock putaway for storage types with the following settings: ■

Storage behavior Standard Warehouse and putaway rule Empty Bin

■

Storage behavior Pallet Storage

If the system cannot find a storage bin for the addition to existing stock, it uses sort sequences to search for a storage bin. This means that you can also define cross-line stock putaway for storage types with the storage behavior Standard Warehouse and putaway rule Addition to Existing Stock/Empty Bin or with the storage behavior Bulk Storage.

Prerequisites ●

You have defined a sort sequence for cross-line stock putaways in Customizing for Extended Warehouse Management (EWM). To do so, you have performed the following steps: a. You have defined an activity for cross-line stock putaway in your warehouse number for the activity CLSP with warehouse process category 8 (Cross-Line Stock Putaway) under Master Data → Activity Areas → Activities → Define Activities. b. You have generated an activity area for the storage type in which you want to perform the cross-line stock putaway under Master Data → Activity Areas → Generate Activity Area from Storage Type. The activity area must match the storage type, in other words, it must contain the same storage bins. The system gives the generated activity area the same name as the storage type. c. You have defined a sort sequence for cross-line stock putaway under Master Data → Activity Areas → Define Sort Sequence for Cross-Line Stock Putaway.

●

You have created a storage bin sorting on the SAP Easy Access screen under Extended Warehouse Management → Master Data → Storage Bin → Sort Storage Bins.

SAP Extended Warehouse Management (SAP EWM)

510

390

SAP Online Help

20.07.2007

Capacity Check Use In the case of some putaway strategies, it is useful to perform a capacity check for the storage bin when searching for a suitable storage bin. If you have activated the capacity check, the system checks whether the selected storage bin can accept the quantity to be put away when it creates a warehouse task (WT).

Prerequisites ●

You can set up the capacity check in Customizing for Extended Warehouse Management (EWM) under Master Data → Define Storage Type (Putaway Control, Capacity Check field). By default, the checks are predefined in accordance with weight and volume.

●

To control the capacity check in accordance with weight or volume, you have defined the following:

●

○

You have defined the weight or volume consumption for each storage bin. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Storage Bin → Create Storage Bin (Stor. Bin tab page, Weight Usage or Volume Usage field).

○

You have defined a weight or volume consumption per unit of measure for each product in the product master. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Product → Maintain Warehouse Product (Units of Meas. tab page).

To control the capacity check in accordance with the capacity key figure, you have defined the following: ○

You have defined a capacity that is independent of a dimension or a unit for each storage bin. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Storage Bin → Create Storage Bin (Stor. Bin tab page, Capacity Usage field).

○

You have defined a capacity consumption per unit of measure for each product in the product master. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Product → Maintain Warehouse Product (Units of Meas. tab page, Capacity Consumption field).

○

You have defined a capacity consumption per unit of measure for each packaging material in the product master. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Product → Maintain Warehouse Product (Units of Meas. tab page).

Features Extended Warehouse Management (EWM) can check the capacity of a storage bin using the following factors: ●

Weight The system checks the weight of the product to be put away against the available weight of the storage bin.

●

Volume The system checks the volume of the product to be put away against the available volume of the storage bin.

SAP Extended Warehouse Management (SAP EWM)

510

391

SAP Online Help ●

20.07.2007

Capacity key figure (see below) ○

Capacity check in accordance with product This capacity check is recommended if you can stack products in the storage bin in any way you like. You can also apply this capacity check if different batches of the product exist that result in mixed storage.

○

Capacity check in accordance with handling unit (HU) This capacity check is recommended if the HUs lie next to one another and you can remove the products one after another from each container.

○

Capacity check in accordance with product and HU

If you work with fixed storage bins or use the putaway strategy Addition to Existing Stock, we recommend a capacity check. In bulk storage, the capacity check is performed via the block definition.

Capacity Check in Accordance with Capacity Key Figure You can also use a capacity key figure to control how a product is put away in a storage bin. Here the system calculates the capacity consumption in different ways, depending on the capacity check chosen: ●

Capacity check in accordance with product The system calculates the capacity consumption for the product on the basis of the quant (quantity of a product with the same attributes).

●

Capacity check in accordance with HU In the case of HU checks, the system calculates the capacity consumption on the basis of the HU.

●

Capacity check in accordance with product and HU In the case of mixed storage, we recommend the capacity check in accordance with the product and HU.

Example 1

Example 2

Example 3

The capacity consumption of a product refers to the product quantity and is therefore specified as a variable in the system, and updated in the quant. The capacity consumption of an HU is specified as a constant capacity consumption, and is updated in the HU.

SAP Extended Warehouse Management (SAP EWM)

510

392

SAP Online Help

20.07.2007

Quant and HU data is updated for each storage bin as remaining capacity. You have to define the type of capacity check as well as the capacity consumption of the product and HU before the first putaway. Subsequent changes to these parameters result in automatic changes to storage bins, HUs, and quants. You must not make such changes when the system is running in productive mode since they result in inconsistencies. For more information about the capacity check in accordance with the capacity key figure, see Examples of Capacity Check in Accordance with Capacity Key Figure [Seite 394].

SAP Extended Warehouse Management (SAP EWM)

510

393

SAP Online Help

20.07.2007

Examples of Capacity Check in Accordance with Capacity Key Figure In the following section, you find an example of each of the three types of capacity check in accordance with the capacity key figure.

Capacity check in accordance with product The storage bin 01-01-01 has a total capacity of 100. Each piece of product 4711 has a capacity consumption of 11. This means that you can put away nine pieces of product 4711 in this storage bin. Here you have a remaining capacity of one. Storage Bin 01-01-01 Total Capacity = 100 Product 4711 Capacity Consumption = 11

9 x 11 = 99 Remaining Capacity = 1

Capacity check in accordance with HU The storage bin 01-01-01 has a total capacity of 100. Each wire basket has a capacity consumption of 12. This means that you can put away eight wire baskets in the storage bin. Here you have a remaining capacity of four. Storage Bin 01-01-01 Total Capacity = 100

Product 4711 HU Capacity Consumption = 12

8 x 12 = 96 Remaining Capacity = 4

SAP Extended Warehouse Management (SAP EWM)

510

394

SAP Online Help

20.07.2007

Capacity check in accordance with product and HU The storage bin 01-01-01 has a total capacity of 100. Each piece of product 4711 has a capacity consumption of eleven. Each pallet has a capacity consumption of 12. You can put way one pallet with eight pieces of product 4711 in the storage bin. As a result, the storage bin no longer has any available capacity. Storage Bin 01-01-01 Total Capacity = 100

Product 4711 Capacity Consumption = 11 HU Capacity Consumption = 12

(8 x 11) + (1 x 12) = 100 Cubic Meters, for example Remaining Capacity = 0

SAP Extended Warehouse Management (SAP EWM)

510

395

SAP Online Help

20.07.2007

Stock Removal Strategies Use You use stock removal strategies [Extern] to define where the system is to search for stock, in other words, in which storage types, and how it is to sort the stock that has been determined. Stock is determined in the following cases: ●

Warehouse task (WT) creation

●

Creation of warehouse requests

●

Changing warehouse request items

Prerequisites You make the settings for the stock removal strategies in Customizing for Extended Warehouse Management (EWM) under Goods Issue Process → Strategies. For more information, see the Implementation Guide (IMG) and the documentation for the individual strategies.

Features The following table shows possible stock removal strategies: Strategy

Comment

FIFO (First In, First Out) [Seite 397]

With FIFO, the system searches for the oldest quant.

Stringent FIFO for All Storage Types [Seite 398]

With stringent FIFO, the system searches across all storage types.

LIFO (Last In, First Out) [Seite 399]

With LIFO, the system searches for the most recent quant.

Partial Quantities First [Seite 400]

The system first searches for partial quantities and then for standard quantities.

Stock Removal Suggestion According to Quantity [Seite 402]

The system determines the storage bin on the basis of the quantity.

Shelf Life Expiration Date [Seite 403]

The system searches for products with the shortest remaining time before the expiration date.

Fixed Storage Bin [Seite 404]

The system searches for a fixed storage bin.

You can use the BAdIs in the /SCWM/ES_CORE_RMS enhancement spot to make changes to these putaway strategies. See Also: Storage Bin Determination for Stock Removal [Seite 343]

SAP Extended Warehouse Management (SAP EWM)

510

396

SAP Online Help

20.07.2007

Strategy: FIFO (First In, First Out) Use In the case of this strategy, the system first proposes the oldest quant from the storage type from which you want to remove products from stock. The system calculates the age of a quant (its retention period in the warehouse) from the date when goods receipt was posted. The goods receipt date is set automatically in the quant and in the warehouse request for each goods receipt posting. You can accept the goods receipt date that the system sets or you can enter a different date. Regardless of whether you adopt the goods receipt date or enter a new one, the system uses this date to calculate the age of the quant. This date influences the sort sequence for each product.

Prerequisites ●

You have defined a stock removal rule in Customizing for Extended Warehouse Management (EWM) under Goods Issue Process → Strategies → Specify Stock Removal Rule. You have specified the goods receipt date (sort ascending) as the sort criterion.

●

You have defined a storage type search sequence in Customizing for EWM under Goods Issue Process → Strategies → Specify Storage Type Search Sequence.

●

You have assigned the storage type search sequence in Customizing for EWM under Goods Issue Process → Strategies → Determine Storage Type Search Sequence for Stock Removal.

●

You have assigned the stock removal rule to the storage type in Customizing for EWM under Master Data → Define Storage Type. Alternatively, you can assign the stock removal rule under Goods Issue Process → Strategies → Determine Storage Type Search Sequence for Stock Removal.

SAP Extended Warehouse Management (SAP EWM)

510

397

SAP Online Help

20.07.2007

Strategy: Stringent FIFO Across All Storage Types Use In Extended Warehouse Management (EWM), you can remove stock according to the FIFO principle where you take into consideration all quants within a warehouse number. In this case, the system does not scan individual storage types in sequence but instead it proposes the oldest quant in the entire warehouse as the quant to be removed from stock.

Prerequisites See Strategy: FIFO (First In, First Out) [Seite 397] You have also defined storage type groups and assigned all relevant storage types to them in Customizing for EWM under Master Data → Define Storage Type Groups.

SAP Extended Warehouse Management (SAP EWM)

510

398

SAP Online Help

20.07.2007

Strategy: LIFO (Last In, First Out) Use For some warehouse organizations or sectors of industry, you cannot use the FIFO principle. For example, in the building material industry, products that are to be removed from stock and are therefore being stored temporarily are stacked on products that are already stored in the warehouse. When using the FIFO strategy, the warehouse worker would first have to remove the products lying on top to get to the product with the oldest goods receipt date. The LIFO strategy is provided for such situations. When the system searches for a suitable quant to remove from stock, it always suggests the last quant that was placed into stock.

Prerequisites See Strategy: FIFO (First In, First Out) [Seite 397] with the exception that you have specified the goods receipt date (sort descending) as the sort criterion.

SAP Extended Warehouse Management (SAP EWM)

510

399

SAP Online Help

20.07.2007

Strategy: Partial Quantities First Use With this strategy, the system overrides the FIFO principle to optimize the management of stock in the warehouse. It keeps the number of partial handling units (partial HUs) in one storage type as low as possible. This strategy is only suitable if putaway meets one of the following conditions: ●

It takes place in the form of standard HU types (always the same quantity of a product for a certain HU type).

●

It takes place in the form of partial pallet quantities (quantities smaller than a standard HU).

There are two different types of quant within a storage type: ●

Quants in the quantity of the standard HU in accordance with packaging specification

●

Quants in a quantity that is smaller than the standard HU. This is known as a partial pallet quantity. Quants that are larger than a standard HU should not occur.

When the system searches for a quant, it proceeds as follows:

...

1. If the required quantity in the warehouse task is the same as or greater than the quantity of a standard HU, the system attempts to remove a standard HU from stock. 2. If no standard HUs exist, the system takes partial pallet quantities. 3. If the required quantity in the warehouse task is less than the quantity of the standard HU, the system first tries to remove partial pallet quantities from stock. 4. If no partial pallet quantities exist, the system breaks into complete HUs.

Prerequisites ●

You have defined a stock removal rule with ascending quantity (piece) and a stock removal rule with descending quantity (standard HU) in Customizing for Extended Warehouse Management (EWM) under Goods Issue Process → Strategies → Specify Stock Removal Rule.

●

You have assigned the stock removal rules in Customizing for EWM under Goods Issue Process → Strategies → Determine Storage Type Search

Sequence for Stock Removal: ○

Stock removal rule “piece” – quantity classification group “piece”

○

Stock removal rule “standard HU” – quantity classification group “standard HU”

•

You have defined a storage type search sequence in Customizing for EWM under Goods Issue Process → Strategies → Specify Storage Type Search Sequence.

●

You have assigned the stock removal rules in Customizing for EWM under Goods Issue Process → Strategies → Determine Storage Type Search Sequence for Stock Removal:

●

You have defined quantity classifications for the warehouse in Customizing for EWM under Cross-Process Settings → Warehouse Task → Define Quantity Classifications.

●

You have defined a packaging specification for the product in Customizing for SCM Basis under Packing → Packaging Specification.

SAP Extended Warehouse Management (SAP EWM)

510

400

SAP Online Help

20.07.2007

Example You use two packaging specification levels, pallet and piece, and you have defined a quantity classification and a stock removal rule for each of them. The system uses the stock removal rule for piece to sort the stock by quantity in an ascending order. The system uses the stock removal rule for pallet to sort the stock by quantity in an descending order. If the quantity required is greater than or equal to the quantity of the complete HU, the system sorts the stock in a descending order, in other words, it removes a full pallet from stock. If the required quantity is smaller than a complete HU, the system sorts the stock in an ascending order, in other words, since a complete HU is not required, the system searches for a partial HU.

SAP Extended Warehouse Management (SAP EWM)

510

401

SAP Online Help

20.07.2007

Strategy: Stock Removal Suggestion According to Quantity Use This strategy is based on whether the quantity required in the warehouse task is large or small. For example, you have a storage type in a warehouse in which you store small quantities of products (a storage type with a fixed storage bin structure). You also have a reserve storage area where you store larger quantities. The system decides whether it is dealing with a small quantity or a large quantity, depending on the quantity required in the warehouse task. It proposes that stock be removed from either the storage bin of the small quantity storage type or from the storage bin of the large quantity storage type. The system uses the quantity of the standard HU in accordance with the packaging specification as the criterion.

Processing Small and Large Quantities The following figure shows the processing of small and large quantities: Quantity to Be Removed from Stock Smaller Than/Equal to Qty of Standard HU Acc. to Packaging Specification

Yes

Fixed Bin Storage

Small Quantities

No

High Rack Storage

Large Quantities

In the example shown in the figure, two storage types are used to fill delivery notes from Sales and Distribution: ●

Fixed bin storage

●

High Rack Storage Area

The system selects the quant from a storage bin in fixed bin storage, if the required quantity is less than or equal to the quantity of the standard HU in accordance with the packaging specification. If the required quantity is greater than the quantity of the standard HU in accordance with the packaging specification, the system searches for the quant in high rack storage.

Prerequisites See Strategy: Partial Quantities First [Seite 400] with the exception that you have defined and assigned two storage type search sequences.

SAP Extended Warehouse Management (SAP EWM)

510

402

SAP Online Help

20.07.2007

Strategy: Shelf Life Expiration Date Use With this strategy, the system ensures that the products with the oldest shelf life expiration date are removed from stock first.

Prerequisites See FIFO (First In, First Out) [Seite 397] with the exception that you have specified the shelf life expiration date as the sort criterion.

SAP Extended Warehouse Management (SAP EWM)

510

403

SAP Online Help

20.07.2007

Strategy: Fixed Storage Bin Use In the case of this strategy, the system uses the storage bin that was entered in the product master to find stock. If you have allowed fixed storage bin assignments for a storage type, the system also takes into consideration the storage bins that do not contain any stock when determining the stock. In this way, it is possible that the system creates warehouse tasks (WTs) for which no stock exists. You use replenishment control to ensure that products are available in the storage bin at the time of picking. Negative available stock is allowed with this strategy. To clear the pick items or the pick quantity per storage bin, you can specify that the system is to sort the stock by open stock removal items per storage bin or by open quantity to remove per storage bin.

Prerequisites ●

You have defined a stock removal rule and, optionally, specified the open stock removal items or the open quantity to remove per storage bin as the sort criterion in Customizing for Extended Warehouse Management (EWM) under Goods Issue Process → Strategies → Specify Stock Removal Rule.

●

You have defined a storage type search sequence in Customizing for EWM under Goods Issue Process → Strategies → Specify Storage Type Search Sequence.

●

You have assigned the storage type search sequence in Customizing for EWM under Goods Issue Process → Strategies → Determine Storage Type Search Sequence for Stock Removal.

●

You have defined fixed storage bins in the master data for EWM under Storage Bin → Maintain Fixed Storage Bin.

●

You have set the Fixed Bins Allowed indicator in Customizing for EWM under Master Data → Define Storage Type. Optionally, you have set the Negative Stock indicator if you want to permit negative available stock.

SAP Extended Warehouse Management (SAP EWM)

510

404

SAP Online Help

20.07.2007

Warehouse Task Definition Document that uses Extended Warehouse Management (EWM) to execute goods movements. Logical or physical goods movements or even stock changes can be the basis for a warehouse task. These include: ●

Picks

●

Putaways

●

Internal goods movements

●

Posting changes

●

Goods receipt postings

●

Goods issue postings

Use You create the warehouse task either with reference to a warehouse request or without a reference document, for example for internal goods movements. The following figure shows the different warehouse tasks for products and handling units (HUs): Product Warehouse Tasks [Seite 406] Handling Unit Warehouse Tasks [Seite 407] PROD WT

HU WT

PROD WT HU WT

HU WT

Product Warehouse Task Handling Unit Warehouse Task

You or the system use product warehouse tasks, for example, for deconsolidation [Seite 298] and handling unit warehouse tasks, for example, for unloading [Seite 608]. You can identify the type of the warehouse task from the warehouse process type in the warehouse task. For more information about the simultaneous use of product warehouse tasks and handling unit warehouse tasks, see Pick Point [Seite 410]. EWM also submits hazardous substance texts [Seite 969] in the warehouse task. When you confirm a warehouse task, you can also perform a physical inventory at the same time [Seite 670]. Here, EWM can work with the low-stock physical inventory.

SAP Extended Warehouse Management (SAP EWM)

510

405

SAP Online Help

20.07.2007

Product Warehouse Task Definition Document that helps Extended Warehouse Management (EWM) move products. A product warehouse task (product WT) can be based on physical goods movements or changes in stock.

Use The product WT contains all the information required to execute the physical transfer of products into the warehouse, out of the warehouse, or within the warehouse from one storage bin to another storage bin. When you confirm a product WT, you inform EWM what you have processed this product WT and that the goods have arrived at their destination. If the planned quantity (target quantity) differs from the actual quantity of stock that is moved, a difference quantity exists. If you confirm a product WT with a difference, the system automatically posts the difference quantity to a “difference interface”. Once confirmed, the product WTs also have a documentation function, since they document movements in the warehouse.

Structure A product WT contains all necessary information about a goods movement to be executed. ●

What should be moved?

●

Which quantity should be moved?

●

From where (source storage bin) should the product be moved, and to where (destination storage bin)?

When you create a product WT, it consists of an item with the source storage bin and destination storage bin. When you confirm a product WT, it consists of either an item with the source destination bin or destination storage bin, or it consists of more than one item in the case of partial confirmations. ●

For goods receipt postings, the product WT consists of an item that increases the stock.

●

For goods issue postings, the product WT consists of an item that decreases the stock.

●

For transfer postings, the product WT consists of two items. One item that decreases the stock, and one item that increases the stock.

●

In the case of partial confirmations, EWM creates one item for each partial confirmation. You create partial confirmations, for example, when you partially pick from a nested handling unit, or when you confirm different pick handling units.

A product WT reserves the quantities, so that these are no longer available for other product WTs.

SAP Extended Warehouse Management (SAP EWM)

510

406

SAP Online Help

20.07.2007

Handling Unit Warehouse Task Definition Document that helps Extended Warehouse Management (EWM) to move handling units (HUs). A handling unit warehouse task (HU WT) is based on goods movements.

Use The HU WT contains all the information required to execute the physical transfer of HUs within the warehouse from one storage bin to another storage bin. As an exception, you can also use the HU WT for the loading and unloading process. When you confirm a HU WT, you inform EWM what you have processed this HU WT and that the goods have arrived at their destination. Once confirmed, the HU WTs also have a documentation function, since they document movements in the warehouse.

Structure An HU WT contains all necessary information about a goods movement to be executed. ●

Which HU should be moved?

●

From where (source storage bin) should the HU be moved, and to where (destination storage bin)?

The HU WT always consists of an item with the source destination bin and destination storage bin. It does not reserve any quantities.

SAP Extended Warehouse Management (SAP EWM)

510

407

SAP Online Help

20.07.2007

Identification Point Definition Place in an automated warehouse at which you identify newly-arrived goods.

Use In many warehouses, certain storage types (such as high rack storage areas) require identification points (ID points). In these warehouse types, you have to use the ID point to execute the putaway of all handling units (HUs). In Extended Warehouse Management (EWM), the ID point is a physical place in a HU-managed warehouse at which you identify goods receipts for further processing. The following figure illustrates the transfer of products from the goods receiving zone to a high rack storage area using an ID point.

GR Zone

High Rack Storage Area

ID Point

1

2

For example, if you have assigned the ID point storage type 0081 to the storage type 0080, and want to put away goods in the storage type 0080, then EWM proposes the ID point storage type 0081.

Structure The purpose of an Identification Point includes the following: ●

Contour control A contour check often occurs at an ID point to determine whether the HU was built correctly.

●

Changing the mode of transport A conveyor equipment change can occur at an ID point. For example, the HUs are loaded from a forklift onto a conveyor.

●

To determine the final destination EWM determines the destination storage bin in the final storage type at the ID point. Since EWM only assigns the destination storage bin after the HU arrives at the ID point, EWM determines the location of the storage bin based on the most current information about the storage type's space availability.

SAP Extended Warehouse Management (SAP EWM)

510

408

SAP Online Help

20.07.2007

Integration ●

You define an ID point in EWM as the storage type “identification point“ in Customizing for EWM under Master Data → Define Storage Types, by setting the storage role Storage Type Is ID Point.

●

You connect the ID point to the HU-managed storage type in which the putaways from the ID point are to occur:

...

a. In Customizing, choose Master Data → Define Storage Types. b. Select the storage type to which you want to assign the ID point. c. Choose ID Point Active. d. In Customizing for EWM, assign your IDpoint to a storage type, by choosing Cross-Process Settings → Warehouse Task → Define Layout-Oriented Storage Control.

For more information about layout-oriented storage control, see Layout-Oriented Storage Control [Seite 340]. For more information about Customizing for layout-oriented storage control, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Warehouse Task → Define Layout-Oriented Storage Control.

SAP Extended Warehouse Management (SAP EWM)

510

409

SAP Online Help

20.07.2007

Pick Point Definition The pick point is the actual place in the warehouse at which you pick items for a partial stock pick from a handling unit (HU).

In an automated high rack storage area (HRSA), the pick point can be a certain point on the conveyor line along which you move the HUs for picking. A pick point can also be a marked floor area to which you bring entire pallets for removal of products.

Use If you cannot execute partial stock picks in a storage type, for example due to physical restrictions in a high rack storage area, you use pick points to pick partial quantities or to repack. The following graphic illustrates how a partial stock pick occurs using a pick point. Shelf Storage

Pick Point

Goods Issue Zone

Remainder

If you only want to pick a portion of the product quantity from the HU, you bring the HU to the HU-managed pick point to carry out the actual picking. ...

1. At the pick point, you pick the required product quantity from the HU and remove the required products to the goods issue zone. 2. After picking, you put away the HU with the remaining product quantity from the pick point back into the warehouse and confirm the HU warehouse task.

Return Transfer of HUs You can putaway partial HUs back into the warehouse after picking at the pick point. ●

You have determined a fixed storage type for the return transfer of HUs, because you have a special storage type for partial HUs, for example. In the Implementation Guide (IMG) for Extended Warehouse Management (EWM), choose Master Data → Work Center → Define Work Center. EWM determines a new storage bin in the storage type and creates a corresponding HU warehouse task with the destination storage bin.

●

You putaway the partial HU back into the same storage type in which you previously removed it.

SAP Extended Warehouse Management (SAP EWM)

510

410

SAP Online Help

20.07.2007

You do not determine a fixed storage type for the return transfer of HUs. EWM determines the storage type as well as the destination storage bin by using putaway strategies [Seite 375].

Integration ●

You define a pick-point in EWM as the “pick point“ storage type in Customizing for EWM, under Master Data → Define Storage Type, by setting the storage role Storage Type Is Pick Point.

●

You link the pick point to the HU-managed storage type from which the stock removals to the pick point are to occur: a. In Customizing for EWM, choose Master Data → Define Storage Type. b. Select the storage type to which you want to assign the pick point. c. Specify Pick Point Active. d. In Customizing for EWM, assign your pick point to a storage type, by choosing Cross-Process Settings → Warehouse Task → Define Layout-Oriented Storage Control.

For more information about layout-oriented storage control, see Layout-Oriented Storage Control [Seite 340]. For more information about Customizing for layout-oriented storage control, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Warehouse Task → Define Layout-Oriented Storage Control. ●

You set your pick point as work center. In Customizing for EWM, choose Master Data → Work Center → Define Work Center.

SAP Extended Warehouse Management (SAP EWM)

510

411

SAP Online Help

20.07.2007

Creation of Warehouse Tasks for Warehouse Request Use Extended Warehouse Management (EWM) uses this function so that when you or EWM release a wave, EWM simultaneously creates warehouse tasks [Seite 405] for stock removal or internal stock movements. EWM creates warehouse orders pursuant to the warehouse tasks, to assemble work packages for the individual warehouse workers. Instead of this standard creation of warehouse tasks through wave release, you can also create a warehouse task as follows: ●

Manually, with the user interface

●

Automatically, by calling a Post Processing Framework action (PPF action)

Features When EWM creates a warehouse task for a warehouse request, it uses putaway strategies [Seite 375] to determine the storage bin, or stock removal strategies [Seite 396] to determine the stock. For more information, see Storage Bin Determination for Putaway [Seite 291] or Stock Determination [Seite 341]. Extract Time Determination The extract time determination calculates the target time effort to execute a stock movement. EWM determines this time for each warehouse task. Warehouse order creation [Seite 419] adds up the extract time of the individual warehouse tasks for a warehouse order. Optionally, warehouse order creation supplements the extract time determination with a setup time that is defined in the warehouse order creation rule. In addition, if resource management is used, a route time is determined based on the resource used. The warehouse order includes the sum of these times. Based on this, EWM determines the latest start time of a warehouse order. The parameters of extract time determination formulas for a warehouse task are dependent on the product, the quantity, the unit to be transported, and geographical dependencies. For more information about Customizing for extract time determination, see the implementation guide (IMG) for EWM under Cross-Process Settings → Warehouse Task → Define Extract Time Determination.

Activities When EWM creates a warehouse task for a warehouse request, it simultaneously updates this warehouse request. EWM carries out this update by updating the document flow. If the document flow update leads to a change in status, EWM updates this change in the warehouse request as well. ●

By default, you or EWM create warehouse tasks by releasing a wave. After a wave is generated, it can be released immediately, either automatically or manually depending on the release methods you have defined for the wave or wave template. For more information, see Processing of Waves [Seite 771].

●

Instead of this standard creation of warehouse tasks through wave release, you can also create a warehouse task as follows:

SAP Extended Warehouse Management (SAP EWM)

510

412

SAP Online Help

20.07.2007

○

If you want to create warehouse tasks manually using the user interface, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task for Warehouse Request and then the desired action (for example, Putaway for Inbound Delivery).

○

If you want to create warehouse tasks automatically by calling a PPF action, on the SAP Easy Access screen, choose Extended Warehouse Management → Print → Display and Process PPF Actions.

SAP Extended Warehouse Management (SAP EWM)

510

413

SAP Online Help

20.07.2007

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

Process ...

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

For more information, see the report documentation.

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

SAP Extended Warehouse Management (SAP EWM)

510

414

SAP Online Help

20.07.2007

Ad Hoc Movement Use Ad hoc movements are unplanned goods movements that you create manually within a warehouse. This means that the decision to make an ad hoc movement is not controlled by the system. Instead, it is triggered manually. Ad hoc movements do not have a preceding document. An ad hoc movement may be necessary for the following reasons: ●

The wrong product is located in the storage bin.

●

You have to take the product to another storage bin due to damage, for example for a quality inspection.

●

You want to take a product to the appropriate storage bin for scrapping.

●

You have to empty an aisle or storage bin for safety reasons.

●

You want to perform unplanned rearrangement movements.

●

You have to clear away stock lying around in the warehouse.

Prerequisites ●

Stock is available for the product to be moved.

●

You have defined a warehouse process type in Customizing for EWM under CrossProcess Settings → Warehouse Task → Define Warehouse Process Type.

●

If you do not enter a source or destination storage bin for ad hoc movement and want the system to determine this automatically, you can control this using stock removal and putaway strategies. For more information about prerequisites, see Putaway and Stock Removal Strategies [Seite 374].

Features In an ad hoc movement, you move the stock of products from one storage bin to another. To be able to reproduce these movements, you manually create a product warehouse task (product WT) or a handling unit warehouse task (HU WT). If you work with HUs, you can also unpack or repack the products belonging to an HU by creating a product WT in the HU WT. The following table shows the significant data for manually creating product WTs and HU WTs: Product WT

HU WT

The system uses the product and source storage data from the stock overview that you have displayed by entering selection criteria. If you do not want the product to be removed from a specific storage bin, you can control the determination of the source storage data using stock removal strategies.

The system takes the HUs and source storage data from the overview.

Warehouse process type

Warehouse process type

Destination storage data (optional)

Destination storage data (optional)

Reason (optional)

Reason (optional)

Source quantity

–

SAP Extended Warehouse Management (SAP EWM)

510

415

SAP Online Help

20.07.2007

You can manually overwrite the values determined by the system. For the values entered manually, the system checks if they match the configuration of the storage type, storage section, and storage bin in question, for example, if mixed storage or receipts are allowed. Immediate confirmation of the WTs is optional. Depending on the warehouse process type, you can confirm WTs directly after they have been created. While a WT is still open, in other words, until you have confirmed it, the assigned product quantity is not available at the source storage bin nor at the destination storage bin, but belongs to reserved stock. After you have confirmed a WT you can no longer delete it. You can, however, cancel it. Radio Frequency Environment In a radio frequency environment, you can also perform ad hoc movements for products and HUs. For more information, see Ad Hoc Movements Using Radio Frequency [Seite 809].

Actions To create a product WT, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task Without Reference → Move Product. To create an HU WT, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task Without Reference → Move Handling Unit.

SAP Extended Warehouse Management (SAP EWM)

510

416

SAP Online Help

20.07.2007

Posting Change for Stocks Use In Extended Warehouse Management (EWM), you can make a posting change for stock, for example: ●

From available stock to blocked stock (for example, in the case of a complaint)

●

From available stock to customs blocked stock [Extern]

Prerequisites ●

You have made the settings for posting changes in the warehouse process type in Customizing for EWM under Cross-System Settings → Warehouse Task → Define Warehouse Process Type. Here you define, for example, whether a warehouse task (WT) is created automatically during the posting change, or whether it is to be created before or after the posting change.

●

You have optionally defined destination data for stocks in conjunction with the warehouse process type that the system is to suggest for posting changes. You make these settings in Customizing for EWM under Internal Warehouse Processes → Default Values for Posting Changes.

Features You make a posting change for stock by changing the relevant stock attributes and then creating the posting change. You can change the following stock attributes, for example: ●

Storage bin

●

Stock type

●

Batch

●

Sales order or project

You want to move stock from available stock to quality inspection stock. You have the following options that you can configure in Customizing. ■

The stock is to remain in the storage bin, but is no longer to be available for picking. In this case, the system does not create a WT and the stock is simply given a different stock type.

■

You want to take the stock to the quality department. In this case, the system creates a WT. There are two options: ○

The system creates the WT and then a posting change is made automatically for the stock when the destination storage bin is confirmed.

○

The stock is booked out of the source storage bin and then the WT is created automatically.

You can make posting changes for stock for which serial numbers exist on a serial number basis. For more information about serial numbers, see Serial Number [Seite 571].

SAP Extended Warehouse Management (SAP EWM)

510

417

SAP Online Help

20.07.2007

Activities To post stocks, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Make Posting Change for Product.

In this transaction, you can choose and make a posting change for both available stock and the entire stock.

SAP Extended Warehouse Management (SAP EWM)

510

418

SAP Online Help

20.07.2007

Warehouse Order Creation Use This function groups together warehouse tasks into warehouse orders, according to your settings in Customizing for warehouse orders [Seite 423], and thus creates optimum work packages for you. For warehouse order creation, you define rules with their relevant criteria. Warehouse order creation is particularly suitable for optimizing processes for picking.

Integration You assign warehouse orders to warehouse workers in resource management.

Prerequisites You have defined the following in Customizing for Extended Warehouse Management (EWM): ●

Number Ranges for Warehouse Orders For more information about defining number ranges for warehouse orders, see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Order → Define Number Ranges for Warehouse Order.

●

Storage Bins For more information about defining number ranges for warehouse orders, see the IMG for EWM under Master Data → Storage Bins.

●

Activity Areas For more information about defining number ranges for warehouse orders, see the IMG for EWM under Master Data → Activity Areas → Define Activity Area.

●

Start Bins To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Storage Bin → Assign Start/End Storage Bin for Activity Area.

Features A wave consists of a number of deliveries. After the wave and wave item have been released (either automatically by EWM or manually by a user), EWM creates warehouse tasks. EWM joins the warehouse tasks together into warehouse orders, according to the warehouse order creation rules (WO creation rules) you have defined. A warehouse order can contain warehouse tasks from more than one delivery. You can create locked warehouse orders resulting from the wave release. You cannot initially continue to process these warehouse orders. You can use a method in the warehouse management monitor [Seite 878] to release the lock on the warehouse orders. If you want to release the lock on a warehouse order, you can select the Unlock WO method, for example, in the warehouse management monitor in the dialog structure under the node Documents → Warehouse Order using the More Methods action menu (see Processing Waves [Seite 771]). During this summarization of the warehouse tasks into warehouse orders, EWM uses the search sequence for WO creation, for example, first rule A, then B, then C. EWM works through the WO creation rules in sequence, as you have defined for each activity area. You can change the sequence subsequently. Filters and limit values control which warehouse tasks and how many warehouse tasks EWM groups together into a warehouse order.

SAP Extended Warehouse Management (SAP EWM)

510

419

SAP Online Help

20.07.2007

The individual WO creation rule can contain sort rules [Extern]. As soon as EWM applies a WO creation rule, it sorts the warehouse tasks according to these sort rules. Since the work packages for the warehouse employee are based on the complete summarization of warehouse tasks into warehouse orders, then after all user-defined WO creation rules have been applied, no warehouse tasks must be left over that are not assigned to a warehouse order. If EWM has applied all the user-defined WO creation rules for the search sequence, and there are still unprocessed warehouse tasks, the system uses a remainder rule [Extern] . This rule creates warehouse orders for the remaining warehouse tasks. EWM summarizes these warehouse tasks according to the following criteria: ●

For each activity area

●

For each queue

●

For each consolidation group [Extern]

If you do not define your own WO creation rules for the current activity area, then warehouse order creation uses a standard rule [Extern] . This rule attempts to group deliveries according to the following criteria: ●

For each activity area

●

For each queue

●

For each delivery

You can use the following parameters to define creation of warehouse orders in detail for your warehouse processes: ●

Sorting rule For more information about defining sorting rules, see the IMG for EWM under CrossProcess Settings → Warehouse Order → Define Sorting Rules for Warehouse Tasks.

●

Filters For more information about item filters or subtotal filters, see Filters for Warehouse Order Creation Rules [Seite 424].

●

Limit value For more information, see Limit Values for Warehouse Order Creation Rules [Seite 425].

●

Parameters for packing You use these parameters to specify the number of handling units for a warehouse order. You specify these parameters in a packing profile, which you assign to a packaging specification. For more information about defining packing profiles, see the IMG for EWM under Cross-Process Settings → Warehouse Order → Define Packing Profile for Warehouse Order Creation.

●

Packing mode

●

Consolidation group During warehouse order creation, the consolidation group influences which warehouse tasks you are permitted to pack together. EWM determines the consolidation group in the delivery, and transmits it to the relevant warehouse tasks.

You define the maximum number of consolidation groups in a warehouse order as the definition of a limit value.

SAP Extended Warehouse Management (SAP EWM)

510

420

SAP Online Help

20.07.2007

You can simulate creation of warehouse orders for your warehouse tasks. You can define control parameters for warehouse order creation. For example, you can activate the log for WO creation for each warehouse number, activity area or warehouse order creation rule, or specify the number of work processes depending on the warehouse number.

Activities ●

EWM creates a list of warehouse requests.

●

EWM groups the warehouse requests into a wave (for example, a wave pick) and releases it.

●

EWM starts warehouse order creation, and uses the wave as a basis for creating a suitable number of warehouse tasks.

●

EWM creates warehouse orders for each warehouse task, according to your Customizing settings, which contain the relevant warehouse tasks. ○

○

●

For more information about making settings for the sorting rules, filters, limit values, parameters for packing, and the packing mode, see the IMG for EWM under Cross-Process Settings → Warehouse Order → ■

Define Sort Rules for Warehouse Tasks

■

Define Filters for Warehouse Order Creation Rules

■

Define Limit Values for the Size of Warehouse Order

■

Define Packing Profile for Warehouse Order Creation, and select an option for Split WT.

■

Define Packing Profile for Warehouse Order Creation, and select an option for Split TO.

For more information about setting the consolidation group, see the IMG for EWM under Goods Receipt → Deconsolidation → Define Number Ranges for Consolidation Group or Extended Warehouse Management → Goods Issue → Define Number Range for Consolidation Groups.

If you want to simulate warehouse order creation for your warehouse tasks, then on the SAP Easy Access screen choose Extended Warehouse Management → Monitoring → Warehouse Management Monitor.

... ...

i.

Choose warehouse number 0001, the monitor SAP and

ii.

Open Documents → Warehouse Tasks.

iii.

In the dialog box, choose the warehouse task status Open and Execute.

iv.

Select one or more open warehouse tasks and choose Other Methods → Simulate Warehouse Order. The WO Create Rule dialog box appears.

v.

Enter a warehouse order creation rule.

Execute.

If you do not make an entry, then EWM executes the warehouse order creation rules according to the search sequence for warehouse order creation rules.

SAP Extended Warehouse Management (SAP EWM)

510

421

SAP Online Help ●

20.07.2007

If you want to define control parameters for warehouse order creation, from the SAP Easy Access choose Extended Warehouse Management → Settings → Warehouse Order → Set Up Control Parameters for Warehouse Order Creation.

SAP Extended Warehouse Management (SAP EWM)

510

422

SAP Online Help

20.07.2007

Warehouse Order Definition Document that represents an executable work package that a warehouse employee should perform at a specific time. The warehouse order consists of warehouse tasks or physical inventory items.

Use When you move products, in other words you or Extended Warehouse Management (EWM) create warehouse tasks, then EWM groups these warehouse tasks together into warehouse orders, and makes them available for processing. When you perform a physical inventory, in other words you create physical inventory items, EWM also groups these physical inventory items together into warehouse orders. You can adjust the scope and type of a warehouse order using the warehouse order creation rules that you have defined in Customizing.

For more information about warehouse order creation rules, see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Order → Define Creation Rule for Warehouse Orders.

Integration The warehouse groups together warehouse tasks or physical inventory items.

Example EWM creates warehouse tasks for an outbound delivery with four delivery items. EWM uses warehouse order creation to assign the resulting four warehouse tasks to a new warehouse order. A warehouse employee receives this warehouse order as a work package to pick the items listed in the delivery.

SAP Extended Warehouse Management (SAP EWM)

510

423

SAP Online Help

20.07.2007

Filters for Warehouse Order Creation Rules Definition The filter for a warehouse order creation rule decides whether Extended Warehouse Management (EWM) processes a warehouse task using a creation rule. Warehouse order creation uses the filters on all warehouse tasks that you have not yet assigned to a warehouse order, and which WO creation should process.

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

SAP Extended Warehouse Management (SAP EWM)

510

424

SAP Online Help

20.07.2007

Limit Values for Warehouse Order Creation Rules Definition The limit value of a warehouse order creation rule specifies the size of a warehouse order.

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

SAP Extended Warehouse Management (SAP EWM)

510

425

SAP Online Help

20.07.2007

Printing Warehouse Orders and Warehouse Tasks Use Extended Warehouse Management (EWM) can use this function to automatically print lists during creation of warehouse orders and warehouse tasks, according to your Customizing settings. These lists contain information about the storage bin to and from which a warehouse employee should move specific goods. You can use this function in the warehouse management monitor, from the user interface for warehouse tasks, to manually print a warehouse order, which also prints all corresponding warehouse tasks. For example, the first printout is damaged, or your require a second printout.

Integration ●

Printing of warehouse orders and warehouse tasks is based on SAPscript texts and SAP Smart Forms as form templates.

●

EWM uses the Post Processing Framework (PPF) for message control.

●

Additionally, EWM uses condition technique in the schedule condition for PPF, in order to determine the printer, the form type, and the spool parameter.

For more information about the structure and Customizing for the Post Processing Framework, see the SAP Library under SAP NetWeaver Components → SAP Web Application Server → Basis Services/Communication Interface (BC-SRV) → SAP Communication: Configuration (BC-SRV) → Business Workplace and Services (BC-SRV-OFC) → Generic Business Tools for Application Developers (BC-SRV-GBT) → Post Processing Framework (BCSRV-GBT). For more information about the condition technique, see the SAP Library under mySAP Customer Relationship Management → CRM Enterprise → Enterprise Sales → Sales Management for Commercial and Industrial Customers → Basic Functions → Condition Technique.

Prerequisites You have made the settings in Customizing for PPF: ●

You have defined the PPF action definitions with the relevant processing types. In Customizing for the PPF action definition, you have defined the following data: ○

Processing time

○

Scheduling

○

Determination Technique

○

Rule type

○

Action Merging

●

You have specified the PPF conditions for the defined PPF action definitions.

●

In Customizing for the condition technique, you have defined the condition tables.

SAP Extended Warehouse Management (SAP EWM)

510

426

SAP Online Help

20.07.2007

In Customizing, you have defined your condition tables from the field catalog, which SAP delivers. You have selected fields from the field catalog as key fields. These fields represent the condition under which the condition technique finds the condition record. If a data record transferred by EWM matches your key fields, then condition technique finds the matching condition record. ●

In Customizing, you have defined condition types, and therefore the access sequence to the condition tables to search.

●

In Customizing, you have assigned the relevant condition schemas to your condition types. The condition schema specifies the conditions that you permit for determining data (such as printer, form type) and specifies the sequence (access sequence) in which condition technique should consider them.

●

In Customizing, you have assigned the condition schema to the application object (warehouse process type, packaging material type, work center).

●

In Customizing, you have defined the condition maintenance group. The condition maintenance group is required for creating condition records. The condition maintenance group specifies the condition tables and therefore the key fields.

●

You have defined the logical conditions that you want to use in the condition records.

●

You have defined warehouse-number-specific print settings (in particular the spool parameters).

Features For printing warehouse orders, the following action definitions are supported in PPF in the application /SCWM/WME in the action profile /SCWM/HU. These action definitions were created for each form type, and thus enable you to simultaneously print several different documents, for example, printing a warehouse order list and printing individual documents for the warehouse order. For each action definition there is also an SAP Smart Forms form. The system only supports printing of SAP Smart Forms. The following table gives you an overview of the action definitions and their corresponding SAP Smart Forms forms. The assignment between action definition and SAP Smart Forms form is specified in the created condition records. Action Definition

Description

SAP Smart Forms Form

WO_MULTIPLE

Print list for warehouse order with serial numbers

/SCWM/WO_MULTIPLE

WO_SINGLE

Print single document for warehouse order with serial numbers

/SCWM/WO_SINGLE

WO_HUSHIP

Print shipping label

/SCWM/WO_HUSHIP

WO_LOAD

Print loading instruction with warehouse tasks

/SCWM/WO_LOAD

WO_UNLOAD

Print unloading instruction with warehouse tasks

/SCWM/WO_UNLOAD

During warehouse order creation, transfer order confirmation, and activation of product warehouse tasks, if you attempt to print during storage control, then you automatically call up PPF. The decision whether to print is dependent on the condition records that are found in the schedule condition. In the following circumstances, PPF triggers the executing method and therefore printing:

SAP Extended Warehouse Management (SAP EWM)

510

427

SAP Online Help

20.07.2007

●

There is a condition record in which the PPF action definition matches the current PPF action definition.

●

The logical condition is entered in the condition record, and is fulfilled.

During printing or repeat printing, you can also execute PPF action definitions for which there are no defined condition records. In this case, the system cannot determine the necessary data such as printer, form name, and spool parameters, and you must enter this data manually. During printing, PPF writes a determination log and a processing log. Since these logs can become extremely large, you can switch them on and off. To do this, use parameter /SCWM/WO_PRT_PROT.

Activities ●

EWM automatically triggers the print run from processing, or you trigger it manually.

●

EWM calls the PPF and transmits the application data.

●

The PPF determines the PPF action definitions you have defined in Customizing for the PPF application /SCWM/WME and the PPF action profile /SCWM/WO.

●

The PPF calls the schedule condition that corresponds to the PPF action definition.

●

In the schedule condition, the PPF calls determination in the condition technique.

●

Determination of the condition technique returns the relevant condition record. This determines the printer, spool parameters, and the SAP Smart Forms form.

●

PPF reads the current application data.

●

PPF determines the function module that corresponds to the SAP Smart Form form, and calls up the application data.

●

PPF saves the action that was executed and the logs that were written.

SAP Extended Warehouse Management (SAP EWM)

510

428

SAP Online Help

20.07.2007

Manual Assembly of Warehouse Orders Use You use this function in the goods receipt process to delete warehouse tasks of different handling units (HUs) from your warehouse orders, and to group them together in a new warehouse order. This allows you to put away the HUs collectively, and Extended Warehouse Management (EWM) is able to determine the optimal putaway path.

Prerequisites ●

You have made sure that putaway warehouse tasks exist and are active for the entire contents of the HU.

●

If EWM is to generate a single warehouse order for all warehouse tasks that belong to the HUs you have specified, you have made sure that the warehouse activity area and queue for these warehouse tasks are identical (see Warehouse Order Creation [Seite 419]).

●

If you want to print warehouse orders using a PPF action, you have scheduled a corresponding PPF action.

Features This function is optimized so that you can operate it using a hand-held scanner that is installed on a keyboard filter. You can specify multiple HUs in the entry field, one after each other. EWM shows you the specified HU in the lower part of the screen, and assigns the HU to a position field, ascending. For example, you scan three HUs. EWM assigns the HU scanned first to position one, the next HU to position two, and the HU scanned last to position three. Make sure that the position of the HU in EWM matches the physical position of the HU in the resource. When you perform putaway, EWM shows you the position in the Radio Frequency dialog (RF dialog). A traffic light shows the status of the warehouse task. ●

Green means that you have specified a valid HU, and that warehouse tasks exist for all products in the HU. EWM has updated screen content for the total weight and total volume, and increased the number of HUs in the new warehouse order that is to be created by one.

●

Red means that you have specified an HU, but that no warehouse task exists for at least one of the products in the HU. EWM does not update the screen content for the total weight and total volume, and does not include the HU in the new warehouse order that is to be created.

Activities ●

On the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Manually Assemble Warehouse Orders.

●

After you have specified all the HUs, choose Save. In doing this, EWM deletes all warehouse tasks of the HUs from your warehouse orders. EWM attempts to generate a warehouse order for all warehouse tasks, and saves the warehouse tasks in this order. EWM displays a success message if appropriate. If EWM generates one warehouse order only, you can take the warehouse order number directly from the message. If EWM generates multiple warehouse orders, the message only contains the number of warehouse orders. In this case, you can get the warehouse order number from the log. EWM updates the screen content.

SAP Extended Warehouse Management (SAP EWM)

510

429

SAP Online Help ●

20.07.2007

You can print the warehouse order in one of the following ways: ○

Using a Post Processing Framework action

○

Manually Choose Work Center → Print Last Warehouse Order. Under Create Action, choose the PPF action you require for printing warehouse orders (see Printing Warehouse Orders and Warehouse Tasks [Seite 426]).

SAP Extended Warehouse Management (SAP EWM)

510

430

SAP Online Help

20.07.2007

Interface Between EWM and Non-SAP Systems Use Extended Warehouse Management (EWM) has an interface (EWM-WCU interface) that you can use to connect automated warehouse systems such as warehouse control units (WCU) to EWM.

Integration The interface allows communication between the connected systems on the basis of the transactional Remote Function Call [Extern] (tRFC). In contrast to synchronous Remote Function Call (RFC), the system saves the data in an intermediate storage area, before sending it to the connected system. This leads to the decoupling of application and communication.

Features Interface Between EWM and Non-SAP Systems (WMS-WCU Interface) You use the EWM-WCU interface to connect automated warehouse systems, such as warehouse control units (WCU) to Extended Warehouse Management (EWM). For more information, see Scenarios for Connecting Non-SAP Systems [Seite 432] and Description of the IDocs [Seite 459].

SAP Extended Warehouse Management (SAP EWM)

510

431

SAP Online Help

20.07.2007

Scenarios for Connecting Non-SAP Systems Use You can use the interface between Extended Warehouse Management (EWM) and non-SAP systems (EWM-WCU interface) to connect different non-SAP systems to EWM. The following scenarios give you an overview of typical ways in which this interface can be used. Non-SAP systems include warehouse systems dependent on EWM, such as warehouse control units (WCU).

Features The EWM-WCU interface supports the following communcation transactions between the systems: ●

Transfer warehouse tasks from EWM to non-SAP system

●

Transfer release of multiple processing from EWM to non-SAP system

●

Transfer cancellation requests from EWM to non-SAP system

●

Create transfer orders in EWM for warehouse tasks reported by non-SAP system

●

Confirm transfer orders in EWM for warehouse tasks reported as complete by nonSAP system

●

Move handling units [Seite 490]

●

Blocking storage units or aisles

●

Cancel transfer orders in EWM for warehouse tasks not reported as complete by nonSAP system

EWM takes on all tasks related to warehouse management. However, warehouse control and execution of driving commands are not part of EWM's tasks. For this reason, the non-SAP systems always represent standalone systems for the SAP system, which can take on control of the product flow, as well as other tasks such as optimizing the stock movenents or additional control mechanisms. The scenarios focus on the task distribution between EWM and the relevant connected nonSAP system. The flexibility of the EWM-WCU interface enables you to make customerspecific adjustments and enhancements. For more information, see Modification Concepts: IDoc Receipt [Seite 484] and Modification Concepts: IDoc Issue [Seite 487].

Activities You determine the task distribution, according to your own requirements, between EWM and the non-SAP system.

SAP Extended Warehouse Management (SAP EWM)

510

432

SAP Online Help

20.07.2007

Connecting a Semi-Automated Warehouse Purpose In a semiautomatic warehouse, you manage the warehouse using Extended Warehouse Management (EWM), whilst a linked non-SAP system performs the actual stock movements. EWM performs all tasks relevant to warehouse management, including: ●

Managing product stocks and storage bins

●

Triggering warehouse movements (stock removal, putaway, stock transfers and posting changes)

●

Determining the storage bins for warehouse movements based on fixed putaway and stock removal strategies

●

Carrying out the inventory

To optimize the processes in the warehouse you use EWM and a non-SAP system to: ●

Connect forklift systems

●

Control automatic conveyors or conveyor equipment

●

Allow picking without any documents, using RF devices

●

Control the product flow

The following describes two variations of the scenario: ●

EWM does not transfer any data using the EWM-WCU interface to the non-SAP system. You can only use this interface to tell EWM that stock movements have been performed.

●

The EWM-WCU interface is used to transfer pending stock movements to the non-SAP system, as well as to report the execution of stock movements to EWM.

Prerequisites You have configured the interface between EWM and the non-SAP system in Customizing for Extended Warehouse Management under Interfaces → Non-SAP Systems → Connect Subsystem.

SAP Extended Warehouse Management (SAP EWM)

510

433

SAP Online Help

20.07.2007

Process Reporting Using EWM-WCU Interface: Putaway EWM

Non-SAP System

Triggers stock movement

Creates WTs for putaway

Prints WT for putaway

Scan pallet slip in non-SAP system Performs stock movement

Reports goods movement WCU Interface /SCWM/WMTOCO

Confirms reported WTs

...

1. EWM creates warehouse tasks (WTs) for the goods movements. 2. You print the warehouse tasks to use as a pallet receipt/issue slip. The destination storage bin for putaway is printed on the pallet slip in the form of a barcode. 3. You transport the pallet to the automatic conveyor. 4. You scan in the barcode with the destination storage bin at the automatic conveyor. 5. The automatic conveyor carries the pallet to the storage bin and puts it away. 6. If the Customizing settings are such that the WT transferred from EWM must be reported to EWM, then the non-SAP system reports the stock movement for the WT using the message type /SCWM/WMTOCO to EWM. The non-SAP system constructs the warehouse task data in the form of an IDoc for the forklift guidance system, and sends this IDoc to EWM. 7. EWM confirms the warehouse task using the data reported using message type /SCWM/WMTOCO.

SAP Extended Warehouse Management (SAP EWM)

510

434

SAP Online Help

20.07.2007

Reporting Using EWM-WCU Interface: Stock Removal EWM

Non-SAP System

Triggers stock movements

Creates WTs for putaway

Prints WT for stock removal

Scan in non-SAP system

Performs stock movement

Reports goods movement WCU Interface /SCWM/WMOCO

Confirms reported WTs

...

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

SAP Extended Warehouse Management (SAP EWM)

510

435

SAP Online Help

20.07.2007

Transferring warehouse tasks for warehouse movements to the external system EWM

Non-SAP System

Triggers stock movements

Creates WTs for the stock movements Transfers WTs to non-SAP system WCU Interface /SCWM/WMTORD Optimizes stock movements

Performs stock movements

Checks any stock movements

Reports goods movements WCU Interface /SCWM/WMTOCO Confirms reported WTs

...

1. EWM creates warehouse tasks (WTs) for the goods movements. 2. EWM transfers the warehouse tasks using the message type /SCWM/WMTORD to the non-SAP system. 3. The external system executes the goods movements in the warehouse on the basis of the transferred data. The forklift control system monitors all of the movements. 4. If the Customizing settings are such that the warehouse task transmitted from EWM must be reported to EWM, then the non-SAP system reports the stock movement for the warehouse task using the message type /SCWM/WMTOCO to EWM. The non-SAP system constructs the warehouse task data in the form of an IDoc for the forklift guidance system, and sends this IDoc to EWM. 5. EWM confirms the warehouse task using the data reported using message type /SCWM/WMTOCO.

Triggering warehouse movements manually via the external system ...

1. If you trigger stock movements manually (for example, due to a stock transfer within a warehouse, or because you are collating remainder quantities to make more room), then you enter the stock movement in the forklift guidance system. 2. The forklift guidance system reports the stock movement to EWM using message type /SCWM/WMTOCO. The non-SAP system constructs the warehouse task data in the form of an IDoc for the forklift guidance system, and sends this IDoc to EWM.

SAP Extended Warehouse Management (SAP EWM)

510

436

SAP Online Help

20.07.2007

3. EWM creates a warehouse task using the data reported using message type /SCWM/WMTOCO, and updates the stock data in the warehouse management system.

SAP Extended Warehouse Management (SAP EWM)

510

437

SAP Online Help

20.07.2007

Connecting a Fully Automated Warehouse Purpose If you want to use Extended Warehouse Management (EWM) in a fully automatic warehouse, consider the warehouse structure and the automatic warehouse functions when deciding how to distribute the warehouse management tasks suitably between EWM and the non-SAP system. In fully automatic warehouses too, EWM takes on the most important tasks of warehouse management: ●

Managing the product stocks

●

Managing storage bins

●

Triggering warehouse movements (stock removal, putaway, stock transfers and posting changes)

●

Carrying out the inventory

●

Determining the storage bins for warehouse movements based on fixed putaway and stock removal strategies

The external system takes over the entire warehouse controlling: ●

Controlling the conveyor equipment

●

Controlling the product flow

●

Optimizing resources

If you want to use EWM with a fully automatic non-SAP system, you should also take account of the scenario Connecting a Fully Automatic Warehouse as a Black Box [Seite 442].

Prerequisites You have configured the interface between EWM and the non-SAP system in Customizing for Extended Warehouse Management under Interfaces → Non-SAP Systems → Connect Subsystem. You have specified how warehouse management tasks will be distributed between EWM and the non-SAP system. Here, the level of automation in the warehouse plays an important role: ●

In simple automatic warehouses, EWM takes on all warehouse management tasks. The non-SAP system only takes on warehouse control, where the warehouse control can be used to optimize the stock movements triggered by EWM. For more information, see Connecting a Semiautomatic Warehouse [Seite 433].

●

For warehouses with more complex warehouse automation, you should take account of the warehouse technology at warehouse task creation. The external system then takes on some of the warehouse management tasks. For this reason, you move products in this kind of storage type using identification points (ID points) and pick points.

SAP Extended Warehouse Management (SAP EWM)

510

438

SAP Online Help

20.07.2007

Process Putaway via ID points EWM

Non-SAP System

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

WCU Interface /SCWM/WMTORD

Scan pallet slip in non-SAP system Determines pallet type Assigns destination storage type Performs stock movement Reports goods movement

WCU Interface

Creates WT for goods movement

/SCWM/WMSUMO

...

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

SAP Extended Warehouse Management (SAP EWM)

510

439

SAP Online Help

20.07.2007

The non-SAP system constructs the warehouse task data in the form of an IDoc for the non-SAP system, and sends this IDoc to EWM. 11. EWM creates the warehouse task for putaway using the data reported using message type /SCWM/WMSUMO, to post the stock movement triggered by the non-SAP system.

Stock removal via a pick point EWM

Non-SAP System

Triggers stock movements Determines type and scope of stock removal Creates WT from warehouse to GI area Transfers WT to non-SAP system

WCU Interface /SCWM/WMTORD

Sends group release

WCU Interface /SCWM/WMRREF

Determines optimum stock removal sequence Removes handling units to pick point Visualizes the items to pick Reports picking to EWM

WCU Interface /SCWM/WMTOCO

Confirms reported WTs

Determines return transfer storage bin for HU with remaining quantity Return transfers HU

Creates WTs for reported return transfer

WCU Interface /SCWM/WMSUMO

Reports return transfer to EWM

...

1. You trigger a stock removal or picking in EWM by, for example, collating the picking of several outbound deliveries into one collective action. 2. EWM creates warehouse tasks (WTs) for the outbound deliveries. 3. EWM transfers the WTs using the message type /SCWM/WMTORD to the non-SAP system. If you want to execute picking on the basis of outbound deliveries, the system treats each warehouse task that is transferred as an independent pick order. If you want to control picking based on other criteria (for example, based on a route), you must ensure that the non-SAP system only picks the transmitted warehouse tasks after EWM has transmitted all the relevant WTs to the non-SAP system.

The non-SAP system can only collate the WTs into a wave after EWM has transmitted the wave release using message type /SCWM/WMRREF. 4. The external system processes the pick order, which can consist of one or more transferred WTs. 5. The non-SAP system optimizes the individual stock movements from the pick order, by specifying the sequence in which the required handling units should be removed from storage.

SAP Extended Warehouse Management (SAP EWM)

510

440

SAP Online Help

20.07.2007

If there is more than one ID point in the system, then the non-SAP system also specifies the assignment of the individual picking transactions and HUs to the available pick points. Only the external system can ensure optimal pick point assignment, since the utilization of the warehousing equipment is at the fore. 6. You execute picking at the pick point. The external system displays the items to be picked on the screen at the pick point. 7. You confirm the pick and enter any differences that occured. 8. The non-SAP system reports execution of picking for the handling units to EWM, using message type /SCWM/WMTOCO. The non-SAP system constructs the warehouse task data in the form of an IDoc for the forklift guidance system, and sends this IDoc to EWM. 9. EWM confirms the warehouse task using the data reported using message type /SCWM/WMTOCO. Return Transfer for Handling Units with Remaining Quantity ...

1. After picking, you take the HUs with remaining quantities to the ID point for return transfer into the warehouse. 2. The external system identifies the HU at the ID point, by way of a contour control. 3. To optimize capacity utilization of the conveyor vehicles during putaway, the non-SAP system assigns the destination storage bin for the HU. 4. The non-SAP system moves the HU to the destination storage bin and puts the HU away. 5. The non-SAP system reports execution of the stock movement for the HU to EWM, using message type /SCWM/WMSUMO. The non-SAP system constructs the warehouse task data in the form of an IDoc for the non-SAP system, and sends this IDoc to EWM. 6. EWM creates the warehouse task for putaway using the data reported using message type /SCWM/WMSUMO, to post the stock movement triggered by the non-SAP system.

Blocking Storage Bins In automatic warehouses, conveyor vehicles often cannot access certain storage bins.

Certain routes for the vehicles are no longer valid, or some bins cannot be reached by the warehouse technology. Since you are performing warehouse management using EWM, you must block these storage bins as quickly as possible in EWM, so that EWM cannot schedule any more stock movements for these storage bins. The non-SAP system transmits the storage bins to block using the message type /SCWM/WMBBIN to EWM. To tell EWM to unblock blocked storage bins, the non-SAP system transmits the storage bins or aisles affected to EWM using message type /SCWM/WMBBIN.

SAP Extended Warehouse Management (SAP EWM)

510

441

SAP Online Help

20.07.2007

Connecting a Fully Automated Warehouse as a Black Box Purpose In your warehouse complex (Warehouse Number [Seite 23]) that you manage using Extended Warehouse Management (EWM), you have set up several different storage types [Seite 25] . For one or more of these storage types, an external system executes all of the warehouse functions and thus takes over the entire warehouse management and warehouse control for this storage type. The automated storage type is connected as a black box to EWM. In this storage type, EWM hands over the entire warehouse management and warehouse control to the non-SAP system. It does this because the storage type is highly automated and so accurate and timely information about the current status of the warehouse technology is required for the stock movements.

If you want to connect this kind of storage type to your warehouse, we recommend that you implement a system that combines warehouse controlling and warehouse management. Since the automated storage type is only a part of your warehouse complex, you can manage the entire warehouse complex (the warehouse number) using EWM. EWM distributes the individual putaway and stock removal transactions to the various sub-storage-types. In storage types not managed by the non-SAP system, EWM takes on all the standard functions. In storage types managed by the non-SAP system, EWM takes on the following functions: ●

Management of summary stocks for each product

●

Triggering and creating warehouse movements

On the other hand, the external system takes over the entire warehouse management and warehouse control within the storage type: ●

Determining the storage bins for the individual warehouse movements

●

Creating warehouse movements within the storage type

●

Carrying out the inventory

●

Controlling the conveyor equipment

●

Controlling the product flow

●

Optimizing resources

When making your decision concerning the type of interface connection, you should also take account of the scenario for Connecting a Fully-Automated Warehouse [Seite 438].

Prerequisites You have defined the automated section of your warehouse as a separate storage type in EWM.

SAP Extended Warehouse Management (SAP EWM)

510

442

SAP Online Help

20.07.2007

●

You can define a fixed storage bin [Extern] for each product in this storage type, to manage the stocks of product in this storage type and to support physical inventory operations.

●

Alternatively, you define several storage bins in the warehouse type, which do not correspond to the physical storage bins. You allow addition to existing stock for this storage type, so that the system always places a product into this storage type. The system cumulates the stocks of a product in a storage bin. This means that a new product always occupies a new storage bin.

The storage bins that you created in EWM for individual products have no meaning for the non-SAP system.

Process EWM

Non-SAP System

Communicates with other SAP application components Triggers goods movement Creates WT (storage bin is not relevant) Transfers WT to non-SAP system

WCU Interface /SCWM/WMTORD

Determines storage bins for putaway and stock rem. Optimizes material flow Performs goods movement

WCU Interface

Reports goods movement to EWM

/SCWM/WMTOCO

Performs physical inventory

Confirms reported WTs Creates WTs for reported differences

WCU Interface /SCWM/WMTOCO

Reports differences to EWM Triggers and performs whse-int. movements

EWM takes on communication with other SAP application components for the entire warehouse number.

Putaway ...

1. You post the goods receipt of the goods in Inventory Management. 2. EWM creates warehouse tasks for putaway and specifies in which storage type the goods are put away. 3. If you have selected the storage type managed by the non-SAP system for putaway, EWM transmits the relevant WT items using the message type [Extern] /SCWM/WMTORD to the non-SAP system.

SAP Extended Warehouse Management (SAP EWM)

510

443

SAP Online Help

20.07.2007

4. The non-SAP system identifies the goods to put away using either the WT number and WT items, or using the transmitted HU number. 5. If EWM reports execution goods movements, then the non-SAP system reports the putaway to EWM using message type /SCWM/WMTOCO.

Stock Removal ...

1. EWM creates a warehouse task (WT) for the stock removal. 2. EWM sends all stock removal WTs relevant for the storage type managed by the nonSAP system to the non-SAP system, using message type /SCWM/WMTORD. 3. The non-SAP system decides the storage bin from which the required products should be removed. 4. The non-SAP system transfers the transfer orders using the message type /SCWM/WMTORD to EWM. 5. EWM confirms the individual items in the warehouse task, using the reported data and actual quantities from the non-SAP system.

Handling Differences If differences occur in the storage type managed by the non-SAP system during physical inventory or during productive operations, the non-SAP system reports these differences to EWM using the message type /SCWM/WMTOCO. EWM uses the reported differences to create a warehouse task, to post the reported differences to a difference interface.

The non-SAP system must not send product movements within the storage type managed by the non-SAP system, because EWM only manages the summary stocks for this storage type.

SAP Extended Warehouse Management (SAP EWM)

510

444

SAP Online Help

20.07.2007

Data Flow: EWM Transmits Data Purpose The data flow via the interface between the non-SAP system and Extended Warehouse Management (EWM-WCU interface) is explained using an example communication process flow for transmitting warehouse task data from EWM to the non-SAP system. For more information about the business background, see Scenarios for Connecting Non-SAP Systems [Seite 432].

Prerequisites You have made the required TCP/IP settings [Seite 448]. For more information, see BC – SAP Communication: Configuration [Extern]. In Customizing, you have defined the ALE interface. In Customizing, you have specified the circumstances in which a warehouse task (WT) is relevant for transmission to the non-SAP system. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Interfaces → Non-SAP Systems → Connect Subsystem. ●

●

For each warehouse number, you can specify that WT items for the following criteria are relevant for transmission to the non-SAP system: ○

For a storage type

○

For a warehouse process type or

○

For combination of storage type and warehouse process type

You define the external system, which receives the WT item.

Process ...

1. When you create a warehouse task (WT) in EWM, the Customizing settings define that the WT or WT item is relevant for transmission to the non-SAP system. 2. During creation of the WT, the system prepares the data to be transmitted, in the form of an IDoc.

For more information about IDocs and their construction, see Description of the IDocs [Seite 459]. 3. The system saves the created IDoc to the database. 4. Asynchronously to creation of the IDoc, the system uses ALE to trigger transmission of this IDoc to the non-SAP system. The system can transfer individual IDocs or collect several IDocs and then transfer them to the external system later. The transmission is based on Remote Function Call. 5. The non-SAP system must be ready to receive the transmitted data with a relevant program. For more information, see Basis → Basis Services/Communication Interface → Remote Communications → The RFC API → Programming with the RFC API [Extern]. 6. The non-SAP system saves the received IDoc data, and sends a receipt confirmation to the SAP system.

SAP Extended Warehouse Management (SAP EWM)

510

445

SAP Online Help

20.07.2007

We recommend that you save the transmitted data in the non-SAP system first, to ensure that transmission of the IDoc and processing of the transmitted data occur separately. 7. Status management for the data received should prevent the external system from processing the data twice. The external system should be able to recognize IDocs that have been transferred by the SAP system before. This is made possible by the unique transaction identification number (transaction ID), which the SAP system assigns for each communication process. For more information, see Basis → Basis Services/Communication Interface → Remote Communications → The RFC API → Transactional RFC Client Programs.

The external system can also recognize double transfers from the IDoc number external system can also use the IDoc number to identify duplicate transfers. Note that an IDoc number is only unique within a single client in an SAP system. If several clients of an SAP system or several SAP systems are involved in the communication with the external system, the IDoc number is no longer unique. In this case the external system cannot recognize IDocs that have been transferred twice from this number.

Error Processing If you receive an IDoc from EWM to a non-SAP system, the following problems can occur: Troubleshooting Symptom

What You Should Know

Update termination in the SAP system during the application

An update termination during creation of a warehouse task does not affect communication with the external system, because the system only creates an IDoc once the source SAP system document exists. The WT and the IDoc are creates in the same LUW, therefore they are updated synchronously.

Error in the ALE interface: Transferred data is syntactically incorrect

Error in the ALE interface: ●

The outbound partner profile for the receiving system

●

The IDoc message type

ALE adopts the IDoc and saves it, but cannot transfer the IDoc to the external system. For more information, see IDoc Error Processing [Seite 477]. For more information, see IDoc Error Processing [Seite 477].

are not defined There is no connection between the SAP system and the external system

The SAP system tries to set up the connection to the external system by running a report in the background at a later time. As soon as the connection between the two systems exists again, the SAP system automatically transfers all IDocs, which have not yet been sent. You can also start this

SAP Extended Warehouse Management (SAP EWM)

510

446

SAP Online Help

20.07.2007 report manually. For more information, see Processing Technical IDoc Errors [Seite 478].

SAP Extended Warehouse Management (SAP EWM)

510

447

SAP Online Help

20.07.2007

Managing TCP/IP Settings As a prerequisite for communication, you make the following TCP/IP settings: ●

In order for the SAP system to find the target system, you must fulfill the TCP/IP prerequisites, in particular the IP addresses must be known in the relevant hosts file.

●

You have entered the name of the gateway and the dispatcher in the services file, for example, sapgw00 and sapdp00.

●

In the standard system, IDocs are sent from the update transaction. Ensure that the TCP/IP link was also created for the update machine.

●

You work in registration mode. This means that the connection between the non-SAP system program and the gateway remains open. For more information, see Registering Server Programs with the SAP Gateway [Extern]. If you do not work in registration mode, then the SAP gateway must have the authorization to start the external program (RFC server) using Remote Shell.

For details on the TCP/IP settings, see the documentation SAP Communication: Configuration [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

448

SAP Online Help

20.07.2007

Managing Transaction Identifiers (TID) Purpose To ensure the security of the data to transfer, you must work with a unique identifier for a communication transaction. This ID allows the receiving system to recognize whether this data has already been received and processed.

Process The following diagram shows the schematic process flow between the sending and receiving system:

SAP Extended Warehouse Management (SAP EWM)

510

449

SAP Online Help

20.07.2007

Sender Sender ( (Client Client) )

Recipient Recipient ( (Server Server) )

Create/Get Create/GetTID TID

(worldwide (worldwideunique uniquenumber) number)

Save SaveTID TIDwith withdata data records recordsto totransfer transfer

Call Callto tothe theserver: server: Transfer data Transfer dataand andTID TID

Save Savedata dataand andTID TID

Everything EverythingOK OK Confirmation: Confirmation: Update status Update status Not NotOK OK

Confirmation: Confirmation: Receive Receivedata data

Send Sendagain again with same with same TID TID

Delete DeleteTID TIDand and data data immediately immediatelyor or at later point at later point

Check: Check:Does DoesTID TIDexist/was exist/wasitit already alreadyprocessed? processed?

Yes Yes

Do Donothing nothing

No No

Process Processdata data

Update UpdateTID TIDstatus status

SAP Extended Warehouse Management (SAP EWM)

510

450

SAP Online Help

20.07.2007

Example For example, communication could be terminated suddenly during the transmission of data for mobile entry of goods receipts. The processor would send the data again to ensure your update in the SAP system. However, if the data had already been received and processed in the the SAP system after the first attempt at sending, the system must be able to recognize this. It should not process the data a second time.

SAP Extended Warehouse Management (SAP EWM)

510

451

SAP Online Help

20.07.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. For more information about the business background, see Scenarios for Connecting NonSAP Systems [Seite 432].

Prerequisites You have defined the necessary TCP/IP settings. For more information, see SAP Communication: Configuration [Extern]. You have configured the ALE interface in Customizing for Extended Warehouse Management under Interfaces → Non-SAP Systems → Connect Subsystem.

Process ...

1. The non-SAP system saves the data relevant for transmission to the SAP system, and prepares this data for transmission as an IDoc. 2. The external system transfers the IDoc with an appropriate program. The transmission is based on Remote Function Call (BC-ABA) [Extern]. For more information, see Programming with the RFC API [Extern]. The central function module is in the ALE layer. As soon as the external system calls the function module on the SAP system side, the external system can transfer several IDocs.

If an IDoc type only supports single transmission, then the IDoc system documentation explicitly states this fact. 3. Status management for the data to be transferred should prevent the external system from not transferring data.

If the non-SAP system cannot successfully transmit IDocs, you must ensure that the non-SAP system transmits these IDocs again at a later point. 4. The SAP system should be able to recognize IDocs that have been transferred by the external system already. This is made possible by the unique transaction identification number (transaction ID), which the SAP system assigns for each communication process. For more information, see Transactional RFC Client Programs [Extern]. The non-SAP system must always flag the transmitted data with this transaction ID. If the non-SAP system re-transmits an IDoc due to a previous problem with communication, then the non-SAP system must specify the same transaction ID again.

The SAP system does not use the IDoc number to recognize a double transfer of IDocs from the external system. 5. The SAP system receives the transmitted IDoc using ALE, saves the IDoc in the database, and reports the receipt of the IDoc to the non-SAP system. 6. Asynchronously to the receipt of the IDoc, ALE transmits the IDoc to EWM, which then takes over processing of the IDoc.

SAP Extended Warehouse Management (SAP EWM)

510

452

SAP Online Help

20.07.2007

7. EWM uses the transmitted data as the basis for creating warehouse tasks. 8. For each IDoc, EWM reports the processing status to ALE. ALE uses the processing status to trigger error processing for the IDoc.

Error Processing If you receive an IDoc from the non-SAP system in EWM, the following problems can occur: Troubleshooting Symptom

What You Should Know

There is no connection between the external system and the SAP system

The non-SAP system should use status management to ensure that the non-SAP system re-transmits the IDocs again at a later point.

Error in the ALE interface:

Although ALE copies the IDoc and saves it, ALE cannot transmit the IDoc to EWM for processing. For more information, see IDoc Error Processing [Seite 477].

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

For more information, see IDoc Error Processing [Seite 477].

are not defined Error in the application for EWM

If processing of the received IDoc did not proceed correctly, EWM transmits the relevant processing status. For more information, see Processing Logical IDoc Errors in EWM [Seite 481].

SAP Extended Warehouse Management (SAP EWM)

510

453

SAP Online Help

20.07.2007

Data Formatting The system transfers data to structures EDI_DC40 and EDI_DD40. Since EDI also uses these structures, this means that some fields are redundant for the EWM-WCU interface. For more information, see Inbound Processing: Technical Realization [Extern]. EDI_DD40 Field

Format

Name

Relevant for Receipt

TABNAM

CHAR 10

Table structure name

Not relevant

MANDT

CLNT 3

Client

Not relevant, but the system transmits the field to the nonSAP system.

DOCNUM

CHAR 16

IDoc number

SEGNUM

CHAR 6

SAP segment number

SEGNAM

CHAR 10

SAP segment name

PSGNUM

CHAR 6

Number of higher-level SAP segment

The system transmits the field to the nonSAP system, but is not required at receipt.

HLEVEL

CHAR 2

Hierarchy level of SAP segment

The system transmits the field to the nonSAP system, but is not required at receipt.

DTINT2

CHAR 2

Empty field for EDI_DD

Not relevant

SDATA

LCHR 1000

Application data

X

Comments

Unique communication number Sequential numbering of IDoc segments is transferred to the external system, but is not required during receipt.

X

X

IDoc segment name

Actual application data in form of IDoc segment

EDI_DC40

SAP Extended Warehouse Management (SAP EWM)

510

454

SAP Online Help

20.07.2007

Field

Format

Name

TABNAM

CHAR 10

Table structure name

MANDT

CLNT 3

Client

DOCNUM

CHAR 16

IDoc number

DOCREL

CHAR 4

IDoc SAP release

STATUS

CHAR 2

IDoc status

DOCTYP

CHAR 8

IDoc type

DIRECT

CHAR 1

Direction

RCVPOR

CHAR 10

Recipient port

RCVPRT

CHAR 2

Partner type of recipient

X

Value: LS

RCVPRN

CHAR 10

Partner number of recipient

X

For example: WM_SUB_0 0 1 for SAP to SUB

RCVSAD

CHAR 21

EDI: Total SADR fields

RCVLAD

CHAR 70

Logical address of recipient

STD

CHAR 1

EDI standard

STDVRS

CHAR 6

Version of EDI standard

STDMES

CHAR 6

EDI message type

MESCOD

CHAR 3

Logical message code

*

You can use both fields to specify a different function module than the standard function module in the ALE service level, in the table for inbound methods, which is used to process IDocs.

MESFCT

CHAR 3

Logical message function

*

You can use both fields to specify a

SAP Extended Warehouse Management (SAP EWM)

Relevant for Receipt

X

Comments

Unique communication number The system transmits the field to the nonSAP system, but is not required at receipt.

Recommended as IDOCTYP

Not relevant

510

455

SAP Online Help

20.07.2007 different function module than the standard function module in the ALE service level, in the table for inbound methods, which is used to process IDocs.

OUTMOD

CHAR 1

Output mode

TEST

CHAR 1

Test indicator

SNDPOR

CHAR 10

Sender port

SNDPRT

CHAR 2

Partner type of sender

X

Value: LS

SNDPRN

CHAR 10

Partner number of sender

X

For example: S11MAND000, if S11 is the sending SAP system

SNDSAD

CHAR 21

EDI: Total SADR fields

SNDLAD

CHAR 70

Logical address of sender

REFINT

CHAR 14

Reference to transfer data

REFGRP

CHAR 14

Reference to message group

REFMES

CHAR 14

Reference to message type

ARCKEY

CHAR 70

EDI archive key

CREDAT

DATS D 8

IDoc creation date

CRETIM

TIMS T 6

IDoc creation time

MESTYP

CHAR 6

Logical message type

X

For example WMTORD for warehouse tasks

IDOCTYP

CHAR 8

Name of basis IDoc

X

For example: WMTOID01 for WTs

CIMTYP

CHAR 8

Name of intermediate structure

RCVPFC

CHAR 2

Partner function of recipient

SNDPFC

CHAR 2

Partner role of

SAP Extended Warehouse Management (SAP EWM)

Not relevant

510

456

SAP Online Help

20.07.2007 sender

SERIAL

CHAR 20

EDI/ALE: Serialization field

EXPRSS

CHAR 1

Override during receipt

You do not have to enter data in all fields of EDI-DC or EDI_DD. Make sure that you initialize any fields in which you will not enter data. If you create IDoc in R/3 systems using transaction /nWE30, the system automatically creates three structures for each IDoc, which the system numbers. For example, for the warehouse task item /SCWM/E1LTORI, /SCWM/E2LTORI, and /SCWM/E3LTORI. /SCWM/E1LTORI is release-independent, /SCWM/E2LTORI is release-dependent, and the system uses /SCWM/E3LTORI for documentation.

We recommend choosing the E2 segment names during transfer of the segment name, since this is independent of the SAP release.

Example If, for example, 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. In doing so, you send one EDI-DC40 record and four EDI_DD40 records per IDoc. The system collates the four IDoc segments together under the unique number of the IDoc or the intermediate document. The corresponding EDI_DC record is also identified from the DOCNUM. You transfer two internal tables with the following construction: EDI_DD40 9000000000123456

/SCWM/E2LTORH

00112345678905011 E

... (WT header data)

9000000000123456

/SCWM/E2LTORI

0001FRASCATI

... (Item)

9000000000123456

/SCWM/E2LTORI

0002BORDEAUX

... (Item)

9000000000123456

/SCWM/E2LTORI

0003CHIANTI

... (Item)

9000000000123457

/SCWM/E2LTORH

00112345678912011 A

... (WT header data)

9000000000123457

/SCWM/E2LTORI

0001CHATEAUNEUF

... (Item)

9000000000123457

/SCWM/E2LTOR

0002BORDEAUX

... (Item)

9000000000123457

/SCWM/E2LTORI

0003SOAVE

... (Item)

9000000000123456

LS

S11MAND002

LS

SUBSYSTEM1

/SCWM/WM TORD

WMTOID01

9000000000123457

LS

S11MAND002

LS

SUBSYSTEM1

/SCWM/WM TORD

WMTOID01

EDI_DC40

SAP Extended Warehouse Management (SAP EWM)

510

457

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

458

SAP Online Help

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

Partner Agreement

Message type

Name

/SCWM/WMTOID01

Inbound and outbound

/SCWM/WMTORD

Warehouse task

/SCWM/WMTCID01

Inbound

/SCWM/WMTOCO

Confirm warehouse tasks

/SCWM/WMCAID01

Inbound and outbound

/SCWM/WMCATO

Cancellation/cancellation request WT

/SCWM/WMBIID01

Inbound

/SCWM/WMBBIN

Block storage bins

/SCWM/WMRRID01

Outbound

/SCWM/WMRREF

Release waves

/SCWM/WMSUID01

Inbound

/SCWM/WMSUMO

Move handling unit

SAP Extended Warehouse Management (SAP EWM)

510

459

SAP Online Help

20.07.2007

IDoc for Sending WTs to a Non-SAP System Definition In Extended Warehouse Management (EWM), you use IDoc /SCWM/WMTOID01 to send data from warehouse tasks from EWM to connected non-SAP systems.

Use EWM creates a warehouse task order for every warehouse movement, regardless of whether the movement is putaway, stock removal, stock transfer, or a posting change. EWM transfers the warehouse task data to the connected external system in the form of IDoc /SCWM/WMTOID01. The external system requires a precise division of warehouse movements according to type. You should differentiate between the warehouse tasks according to the respective warehouse movement type. ●

●

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, which you have defined in the definition of the movement for connection to the interface.

Which IDoc the system fills and sends to the external system depends on several criteria: Criteria Warehouse movement type

Warehouse process type

Details ●

Putaway

●

Stock removal

●

Stock transfer

●

Posting change

Defining the warehouse process type You define, for example, whether the goods receipt date should be set during putaway.

Cause of the warehouse task

Handling-unit-managed storage types

●

Manual WT

●

WT for inbound or outbound delivery

●

WT for warehouse process type

If HU-managed storage types are affected by the warehouse movement, the system transfers the numbers of the storage units involved. ●

For putaway in HU-managed storage types, the system transfers the HU number in field NLENR.

●

For stock removals from HUmanaged storage types, the system

SAP Extended Warehouse Management (SAP EWM)

510

460

SAP Online Help

20.07.2007 transfers the HU number in field VLENR. ●

For stock transfers between HUmanaged storage types, the system transfers the HU number in both fields.

If you transfer the complete HU, both HU numbers are the same. If you transfer material from one HU to another, the system transfers both HU numbers involved.

You determine the content on the IDoc for the individual customers. We recommend creating test warehouse tasks for transmission to the external system, so that you can check the content of the IDocs, which the system creates.

Structure Message Type You define the partner agreement outbound for message type /SCWM/WMTORD.

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

Format

Description

Required Entry

Comments

LGNUM

CHAR 3

Warehouse number

X

Activate linkage in warehouse number first

WHO

NUMC 10

Warehouse order

QUEUE

NUMC 10

Queue

BNAME

CHAR 12

User name

Fields for segment /SCWM/E2LTORI0004 (WT items) Field

Format

Description

TANUM

NUMC 12

Warehouse task

PROCTY

CHAR 4

Warehouse process type

MATNR

CHAR 40

Product

ENTITLED

CHAR 10

Party entitled to dispose

ENTITLED_ROLE

CHAR 2

Partner role

SAP Extended Warehouse Management (SAP EWM)

Required Entry

Comments

510

461

SAP Online Help

20.07.2007

OWNER

CHAR 10

Owner

OWNER_ROLE

CHAR 2

Partner role

CHARG

CHAR 10

Batch

LETYP

CHAR 4

Handling unit type

ANFME

QUAN 31

Requested quantity

ALTME

UNIT 3

Alternative unit of measure (AUoM)

OPUNIT

UNIT 3

Operative unit of measure (UoM)

VSOLA

QUAN 31

Target quantity in AUoM

VSOLM

QUAN 31

Target quantity in base UoM

MEINS

UNIT 3

Base unit of measurement

VLTYP

CHAR 4

Source storage type

VLBER

CHAR 4

Source storage section

VLPLA

CHAR 18

Source storage bin

NLTYP

CHAR 4

Destination storage type

NLBER

CHAR 4

Destination storage section

NLPLA

CHAR 18

Destination storage bin

VLENR

CHAR 20

Source HU

NLENR

CHAR 20

Destination HU

TRART

CHAR 1

Warehouse process category

PROCS

CHAR 4

External warehouse process

PRCES

CHAR 4

Warehouse process

WDATU

DATS 8

GR date

WDATZ

TIMS 6

GR time

VFDAT

DATS 8

Expiration date

ZEUGN

CHAR 10

Certificate number

SAP Extended Warehouse Management (SAP EWM)

510

462

SAP Online Help

20.07.2007

KOMPL

CHAR 1

Complete indicator

SQUIT

CHAR 1

Confirmation indicator

KZQUI

CHAR 1

Confirmation requirement

MAKTX

CHAR 40

Product description

DOCCAT

CHAR 3

Reference document category

DOCNO

CHAR 35

Reference document number

ITEMNO

CHAR 10

Reference document item

KZNKO

CHAR 1

Zero stock check

CAT

CHAR 2

Stock type

STOCK_DOCCAT

CHAR 3

Document category

STOCK_DOCNO

CHAR 35

Document number

STOCK_ITEMNO

CHAR 10

Document item

Segment definition /SCWM/E2LPHUX000 (pick-handling unit) Field

Data Type

Description

Required Entry

Comments

LGNUM

CHAR 3

Warehouse number

X

Switch on linkage in warehouse number

WHO

CHAR 10

Warehouse order

HUIDENT

CHAR 20

Pick-handling unit

HUKNG

NUMC 3

HU identification

PMAT

CHAR 40

Packaging material

ANZHU

NUMC 3

Number of pick-HUs to create

KZRTN

CHAR 1

Confirmation to subsystem

Segment definition /SCWM/E1LCRSE (serial numbers for warehouse tasks) Field

Data Type

Description

SERID

CHAR 30

Serial number

SAP Extended Warehouse Management (SAP EWM)

Required Entry

Comments

510

463

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

464

SAP Online Help

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

Use The external system triggers warehouse movements in a warehouse type and executes the physical transportation of products. Only then does the non-SAP system transfer the data on the warehouse movements 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, in order to execute the physical warehouse movements and post the storage bins involved. EWM creates a warehouse task from the IDoc data it received and immediately confirms it. You can also create warehouse tasks with incomplete entries in the non-SAP system and send these to EWM. In this case, EWM, as leading system, adds the missing entries (for example, the coordinates of the destination storage bin) and sends the complete WT back to the external system. The non-SAP system confirms the WT, completing the warehouse movement.

Structure Message Type You define the partner agreement inbound for message type /SCWM/WMTORD.

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, see IDoc for Sending WTs to a Non-SAP System [Seite 460].

Only use warehouse process types for this IDoc, which allow immediate confirmation. The physical stock movement has already taken place when you receive information on a warehouse task from the non-SAP system in EWM.

SAP Extended Warehouse Management (SAP EWM)

510

465

SAP Online Help

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

Use You use this IDoc to report executed warehouse tasks (WTs) to EWM. EWM uses this reported data to confirm this WT.

Prerequisites In Customizing for Extended Warehouse Management, under Master Data → Define Storage Type or Cross-Process Settings → Warehouse Task → Define Warehouse Process Type, you have specified which warehouse tasks are subject to a confirmation requirement. When sending the WT data, 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.

Confirmation of Handling Units If you work with handling units (HUs) in your warehouse and move the entire handling unit, then you for this stock movement you confirm a warehouse task for the entire HU. If the HU is a mixed HU and you move individual products, then there are several warehouse tasks for this handling unit. You confirm the relevant warehouse task for each stock movement. During execution of the warehouse tasks, if you notice differences in the handling unit, then you confirm the entire handling unit and enter the difference quantity for those items where you noticed a difference.

Confirmation Without HU Management For stock removals, you confirm entire warehouse tasks. For putaway, you can confirm the WTs item by item, if you are putting away several pallets in your warehouse using one warehouse task. During confirmation of entire WTs, you can enter differences for individual WT items.

Confirmation of Products Managed in Batches If you confirm batch-managed products during goods movements in a HU-managed bulk storage type, you transmit the batch number of the removed products with the confirmation data. You use the CHARG field (report batch for bulk storage) in segment /SCWM/E2LTCCOI004.

Confirmation in a HU-Managed Bulk Storage Area You report the picked HUs to EWM when you confirm the warehouse task. If the reporting of individual HUs is completed for a WT item, set the BQUIT field in the segment /SCWM/E1LTCOI. In this case, you report the WT item by item. There can be several reports for each WT item. Only one report is allowed for each picked HU.

SAP Extended Warehouse Management (SAP EWM)

510

466

SAP Online Help

20.07.2007

If the products are managed in batches, then you transfer the batch number of the products moved when you transfer the confirmation data. You use the CHARG field (report batch for bulk storage) in segment /SCWM/E2LTCCOI004.

Structure Message Type You define the partner agreement inbound for message type /SCWMWMTOCO.

Segments The IDoc for transferring confirmation is constructed as follows: ●

/SCWM/WMTCID01 (as of SAP APO 3.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

Data Type

Description

Required Entry

LGNUM

CHAR 4

Warehouse number

X

LENUM

CHAR 20

Handling unit

X

QNAME

CHAR 12

User name for the confirmation

SQUIT

CHAR 1

Confirm entire HU

NLPLA

CHAR 18

Destination storage bin

NLENR

CHAR 20

Destination handling unit

X

Comments

Value: ‘X’ The destination storage bin refers to the different storage bin for the complete HU (Customizing)

Segment definition /SCWM/E2COHU000: HU data for each WT item Field

Data Type

Description

LBNUM

NUMC 12

WT number

VONHU

CHAR 20

Source HU

NACHU

CHAR 20

Destination HU

HUENT

CHAR 1

Remove entire HU

MENGA

QUAN 31

Quantity

SAP Extended Warehouse Management (SAP EWM)

Required Entry

Comments

510

467

SAP Online Help

20.07.2007

ALTME

CHAR 3

Alternative unit of measure (AUoM)

DMEGA

QUAN 31

Difference quantity

PAPOS

NUMC 4

Sequential number of the HU data line within a WT item

Segment definition /SCWM/E2LTCOH000: WT header (released as of SAP R/3 4.6A) Field

Data Type

Description

Required Entry

LGNUM

CHAR 4

Warehouse number

X

WHO

CHAR 12

Warehouse order

QNAME

CHAR 12

User name for the confirmation

SQUIT

CHAR 1

Indicator: Confirm entire warehouse task

X

Comments

If the entire warehouse task is to be confirmed. (Version 2, 3, and 5)

Segment definition /SCWM/E2LTCOI0004: WT items Field

Data Type

Description

Required Entry

Comments

LBNUM

CHAR 12

Warehouse task

SQUIT

CHAR 1

Indicator: Confirm without difference

X

If the item is to be confirmed without any differences

NISTA

QUAN 31

Destination actual quantity

X

If there are differences in the destination storage bin

NDIFA

QUAN 31

Destination difference quantity

X

If there are differences in the destination storage bin

KZNUL

CHAR 1

Indicator: Bin empty on zero stock check

X

If there is a zero stock check

ALTME

CHAR 3

Unit of measure

X

If quantity is entered

KZDIF

CHAR 1

Differences indicator

X

If you want to post differences to certain interim record for differences

LENUM

CHAR 20

Handling unit number

X

In case of confirmation in bulk

SAP Extended Warehouse Management (SAP EWM)

510

468

SAP Online Help

20.07.2007 storage

VQUIT

CHAR 1

Confirmation in bulk storage area, pick entire HU

NLPLA

CHAR 18

Destination storage bin

PAPOS

NUMC 4

Sequential number of the HU data line within a WT item

PARTI

CHAR 1

Confirming a partial quantity for a WT item

CHARG

CHAR 10

Report batch number for bulk storage area

X

In case of confirmation in bulk storage If the destination storage bin differs from that suggested by the system

Only relevant for handling units (HUs)

Segment definition /SCWM/E1LEXCP: (Exception during warehouse task confirmation) Field

Data Type

Description

TANUM

NUMC 12

Warehouse task

PAPOS

NUMC 4

Sequential number of the DB data line within a WT number

EXCCODE

CHAR 4

Exception code

BUSCON

CHAR 3

Business context

EXEC_STEP

CHAR 2

Execution step in business context

Required Entry

Comments

Segment definition /SCWM/E1LEXCP: (Serial numbers for warehouse task confirmation) Field

Data Type

Description

TANUM

NUMC 12

Warehouse task

PAPOS

NUMC 4

Sequential number of the DB data line within a WT number

DIFF

CHAR 1

Checkbox

SERID

CHAR 30

Serial number

SAP Extended Warehouse Management (SAP EWM)

Required Entry

Comments

510

469

SAP Online Help

20.07.2007

IDoc for Canceling Warehouse Tasks Definition Using IDoc /SCWM/WMCAID01, you can send a cancellation request to an external system, or confirm execution of a cancellation movement to Extended Warehouse Management (EWM).

Use When physical stock movements are executed via the connected non-SAP system, EWM cannot determine whether the warehouse tasks (WTs) transferred to the non-SAP system have already been executed. For this reason, the EWM can only send a cancellation request to the non-SAP system. The non-SAP system then decides whether or not the movement has already been executed. If the stock movement has already been executed, 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, the user receives a corresponding message in EWM. You decide for each individual case what should happen with a WT item that cannot be cancelled. In this case, you make the necessary adjustments manually in the system.

You can only cancel warehouse tasks (WTs) if they have not yet been confirmed.

Sending a Cancellation Request from EWM to the Non-SAP System To send a cancellation request from EWM, fill the following fields in IDoc /SCWM/WMCAID01: Segment

Field

/SCWM/E2LTCAH

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, fill the following fields in IDoc /SCWM/WMCAID01: Segment

Field

/SCWM/E2LTCAH

LGNUM WHO CANCL

/SCWM/E2LTCAI

LBNUM

You can also cancel a warehouse task from the non-SAP system and send the cancellation to EWM, even if EWM has not sent a cancellation request first.

Structure Message type You define message type /SCWM/WMCATO for the inbound and outbound partner profile.

SAP Extended Warehouse Management (SAP EWM)

510

470

SAP Online Help

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

Data Type

Description

Required Entry

Comments

LGNUM

CHAR 3

Warehouse Number

X

WHO

CHAR 12

Warehouse order

X

CNAME

CHAR 12

User name for WT cancellation

CANRQ

CHAR 1

Request cancellation warehouse task

X

X for cancellation request

CANCL

CHAR 1

Response cancellation warehouse task

X

X for cancellation from external system

Comments

Segment definition /SCWM/E2LTCAI000 Field

Data Type

Description

Required Entry

LBNUM

CHAR 12

Warehouse task

X

VLENR

CHAR 20

Source HU

X

NLENR

CHAR 20

Destination HU

X

SFEHL

CHAR 1

Error during cancellation

SFTXT

CHAR 80

Error text for cancellation

SAP Extended Warehouse Management (SAP EWM)

This text appears in the inbox for error messages

510

471

SAP Online Help

20.07.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. The system sends the group number to the header data of the warehouse task to be created.

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.

Features You group together the warehouse tasks into a wave so that you can execute the goods movements for these WTs in one step. For example, processing warehouse tasks for a certain shipping point or removing stock in the same interim storage type. In this case, you are not permitted to execute the goods movement immediately after the non-SAP system receives the warehouse task data. You use the IDoc /SCWM/WMRRID01 to trigger the start of the stock movements for a certain wave by releasing the wave.

Structure Message type You define the partner agreement outbound for message type /SCWM/WMRREF.

Segments The IDoc is made up of segment /SCWM/E1LRRFX. Segment definition /SCWM/E2LRRFX000 Field

Data Type

Description

LGNUM

CHAR 3

Warehouse Number

WAVE

CHAR 10

Wave

DATUM

CHAR 8

Date

UZEIT

CHAR 6

Time (clock-time)

L2KSR

CHAR 1

Relevance for two-step picking

LSKSO

CHAR 1

Two-step picking: Release approval level

SAP Extended Warehouse Management (SAP EWM)

Required Entry

Comments

510

472

SAP Online Help

20.07.2007

IDoc for Blocking Storage Bins Definition Using 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).

Use When, for example, certain storage bins or aisles are inaccessible for the external system due to technical problems, 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. As soon as the storage bins are available again, the external system triggers the unblocking of the non-SAP system by EWM via IDoc /SCWM/WMBIID01.

Structure Message type You define the partner agreement inbound for message type /SCWM/WMBBIN.

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. To block storage bins, set the BLOCK indicator. To unblock storage bins, set the DEBLO indicator.

●

/SCWM/E1LBINI (blocking storage bins IDoc items) To block certain storage bins individually, transfer a /SCWM/E1LBINI segment for each storage bin.

Segment definition /SCWM/E2LBINH000 Field

Data Type

Description

Required Entry

Comments

LGNUM

CHAR 4

Warehouse Number

X

LGTYP

CHAR 4

Storage type

X

BLOCK

CHAR 1

Blocking storage bins

X

Either BLOCK or DEBLO

DEBLO

CHAR 1

Unblocking storage bins

X

Either BLOCK or DEBLO

Segment definition /SCWM/E2LBINI000 Field

Data Type

Description

Required Entry

Comments

LGPLA

CHAR 18

Storage Bin

X

Entry also generic, for example 01

SAP Extended Warehouse Management (SAP EWM)

510

473

SAP Online Help

20.07.2007

SKZUA

CHAR 1

Block indicator: For stock removal

x

At least one of the three indicators

SKZUE

CHAR 1

Block indicator: For putaway

x

At least one of the three indicators

SKZSI

CHAR 1

Blocking indicator: Current inventory

x

At least one of the three indicators

SPGRU

CHAR 1

Blocking reason

Set at least one of the three indicators. To block a range of storage bins, use *. For example, enter 01* to block all storage bins, which begin with 01.

SAP Extended Warehouse Management (SAP EWM)

510

474

SAP Online Help

20.07.2007

IDoc for Stock Movement with HUs Definition You use the IDoc /SCWM/WMSUID01 to report movements of handling units (HUs), for example, stock transfers, from the non-SAP system to Extended Warehouse Management (EWM).

Use Prerequisites You have constructed the HU in EWM, which you want to move in the non-SAP system. The data for the HU is known in EWM.

Features If you trigger a stock transfer of HUs in the non-SAP system, 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, then the non-SAP system reports the stock movement data to EWM. In certain cases it is necessary to trigger a stock transfer of HUs in the non-SAP system. During putaway of pallet, 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 must report the movement performed for the HU to EWM. EWM subsequently posts the reported HU movement in the system.

Putaway Using an Identification Point (ID Point) If you put the HU away using an ID point, then instead of IDoc /SCWM/WMSUID01, you can call the function module /SCWM/_TO_CREATE_MOVE_SU synchronously in EWM. This means that you can prevent accidental duplicate postings in EWM. ...

1. EWM reports the warehouse task for putaway at the ID point to the non-SAP system, and prints the pallet slip. 2. The non-SAP system identifies the pallet and performs a check of the pallet outline. 3. The non-SAP system changes the HU type of the pallet according to the results of the outline check, or specifies the destination storage bin for the pallet in the high rack storage area. 4. The non-SAP system calls function module /SCWM/TO_CREATE_MOVE_SU synchronously. a. If the EWM has priority, then EWM reports the destination storage bin for the pallet to the non-SAP system. b. If the non-SAP system has priority and is waiting for a successful posting of the destination storage bin in EWM, then the non-SAP system transmits the destination storage bin in the high rack storage area to EWM. If the HU has already been put away from the ID point, the function module reads the relevant destination storage bin and reports it to EWM.

Structure Message type You define the partner agreement inbound for message type /SCWMWMSUMO.

Segments The IDoc consists of the segment /SCWM/E1LSUMX with the following fields:

SAP Extended Warehouse Management (SAP EWM)

510

475

SAP Online Help

20.07.2007

Segment definition /SCWM/E2LSUMX001 (Move Handling Unit IDoc Segment) Field

Data Type

Name

Required Entry

LGNUM

CHAR 3

Warehouse Number

X

LENUM

CHAR 20

Handling unit

X

PROCTY

CHAR 4

Warehouse process type

X

LETYP

CHAR 4

HU Type

BNAME

CHAR 12

User name

KZQUI

CHAR 1

Indicator: confirmation required

NLTYP

CHAR 3

Destination storage type

NLBER

CHAR 3

Destination storage section

NLPLA

CHAR 10

Destination storage bin

NLENR

CHAR 20

Destination HU

SAP Extended Warehouse Management (SAP EWM)

Comments

You do not always need to transmit this field.

You do not set this field, since the transmitted stock movement has already been performed and is therefore no longer subject to confirmation.

510

476

SAP Online Help

20.07.2007

IDoc Error Processing TCP/IP Errors The basis for IDoc transmission between systems is TCP/IP. If an error occurs during the transfer, the connection between the sending system and the receiving system is interrupted. Based on return codes in the RFC function used, you can see in the sending system whether an RFC call has worked. If there are TCP/IP errors, break the connection and send the IDoc again.

Technical Errors If errors occur in the ALE service layer during sending or receiving of IDocs, then there is a technical error. If a technical error occurs, Extended Warehouse Management (EWM) sends a workflow work item for each incorrect IDoc in the form of an error message. The system sends this message to all responsible users. Based on the error message, the user can analyze the error and post the document subsequently. For more information, see Processing Technical IDoc Errors [Seite 478].

Logical Errors The system saves a received IDoc in the database before the IDoc has actually been processed. The system breaks off communication with the external system before the transferred data is then processed. If an error occurs during processing of an IDoc in the application system (EWM), then there is a logical error. In this case, EWM creates a workflow work item for each incorrect IDoc. For more information, see Processing Logical IDoc Errors in EWM [Seite 481].

SAP Extended Warehouse Management (SAP EWM)

510

477

SAP Online Help

20.07.2007

Processing Technical IDoc Errors Use During communication between the non-SAP system and Extended Warehouse Management (EWM), errors can occur in the ALE layer. 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, the system checks the syntax of the individual IDocs. The IDoc definition specifies the syntax of the IDoc. 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. IDocs with incorrect syntax cannot be repaired. You correct the IDoc structure in the SAP system and send the IDoc again.

We recommend only switching on the syntax check during testing of IDocs created yourself. You activate the syntax check via the partner profile for one IDoc type and one particular partner. To do this, on the SAP Easy Access screen, choose Tools → ALE → ALE Administration → Runtime Settings → Partner Agreement.

IDoc status 29: Missing or incorrect partner agreement When you send IDocs from the SAP system to the non-SAP system, you must have defined the outbound section of the partner agreement for the message type and all relevant partners. To do this, on the SAP Easy Access screen, choose Tools → ALE → ALE Administration → Runtime Settings → Partner Agreement. If the system cannot find the partner (that is, the connected partner system) for sending the IDocs, proceed as follows: ●

Define the missing partner profile.

●

You retrigger sending of all pending IDocs that you could not send before. For this error, 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. You trigger subsequent sending of the IDocs that contained errors from the inbox. During this subsequent sending, the system flags the incorrect IDoc with the status 31, and copies the IDoc into a new IDoc, to which the system adds the data from the partner agreement and transmits to the asynchronous RFC.

SAP Extended Warehouse Management (SAP EWM)

510

478

SAP Online Help

20.07.2007

Errors in partner profiles only occur in the test run.

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, the system cannot transmit the IDoc to the asynchronous RFC. The system cannot send the IDoc. and there is no official entry in the RFC valuation (/nSM58) for the relevant subsystem. You trigger transmission of the IDoc using report RSEOUT00. Choose Tools → Business Communication → IDoc Basis → Test → Outbound from IDoc, to manually start the report, or schedule a regular background job for the report. Check the outbound processing mode for the IDoc in the partner profile. ●

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. IDocs are not intended to be sent directly.

Status 30 in the IDoc can only occur if outbound mode is set to 4.

Error During Inbound IDoc Processing IDoc status 60: Syntax error in IDoc On sending and receiving IDocs, the system checks the syntax of the individual IDocs. The IDoc definition specifies the syntax of the IDoc. 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 with incorrect syntax cannot be repaired. You correct the IDoc structure in the SAP system and send the IDoc again.

You activate the syntax check via the partner profile for one IDoc type and one particular partner. We recommend that you activate the syntax check for all IDocs you create yourself.

IDoc status 63: Missing or incorrect partner profile When you send IDocs in the SAP system from the non-SAP system, you must have defined the inbound section of the partner agreement for the message type and all relevant partners. To do this, on the SAP Easy Access screen, choose Tools → ALE → ALE Administration → Runtime Settings → Partner Agreement. If the system cannot find the partner (that is, the connected partner system) for receiving the IDocs, proceed as follows: ●

Define the missing partner profile.

●

You retrigger receiving of all pending IDocs that you could not process before. For this error, 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. From the inbox, you trigger the subsequent transmission of the IDocs which contained errors.

SAP Extended Warehouse Management (SAP EWM)

510

479

SAP Online Help

20.07.2007

Errors in partner profiles only occur in the test run.

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, the system cannot transmit the IDoc to the application. You trigger transmission of the IDoc using report RBDAPP01. To do this, plan a regular job in background processing for this report. 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. IDocs are not intended to be transmitted directly to the application.

Status 64 in the IDoc can only occur in conjunction with processing mode 3 and output mode 2.

SAP Extended Warehouse Management (SAP EWM)

510

480

SAP Online Help

20.07.2007

Processing Logical IDoc Errors in EWM Use If you receive an IDoc from the non-SAP system in the SAP system, 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, because EWM responds to missing or incorrect Customizing settings beforehand. The system flags the incorrect IDocs with status 51.

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.

Along with the IDoc, you transmit a stock movement with a warehouse process type from the non-SAP system, which is unknown in the SAP system. ●

The received IDoc data does not match the Customizing settings in the SAP system.

The stock movement reported by the external system is defined for immediate confirmation. However, the warehouse process type in EWM does not permit immediate confirmation for this stock movement.

Procedure ...

1. You correct the relevant Customizing settings. 2. 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.

Missing or Incorrect IDoc Data If the data in the received IDoc is not complete, you decide whether the system should resend the incorrect IDoc, or whether a correction in the SAP system is useful and possible. ●

You make the corrections to the IDoc using the IDoc editor.

Only correct the IDoc using the IDoc editor in exceptional cases. ●

You can subsequently post IDocs of the type WMIVID01 on reporting physical inventory data and correct the data in the relevant transaction.

SAP Extended Warehouse Management (SAP EWM)

510

481

SAP Online Help

20.07.2007

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

Error Due to Blocked Objects If blocking problems occur in the SAP system, IDoc processing leads to an error.

If there are concurrent attempts (by different users) to access the same SAP object, the system terminates processing, with an error note for the blocked object.

Procedure You do not need to intervene manually. Schedule report RBDMANIN for periodical background processing. 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.

Important Error Notes in Inbox For the errors listed above, the system creates a workflow work item in the inbox of the person responsible. For more information, see Rule Resolution in Exception Handling [Extern]. 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.

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. The external system transmits the messages via message type WMINFO.

If the system can no longer confirm a warehouse task or handling unit because the confirmation has already been made, the non-SAP system triggers an internal message. Ensure that the system stores this information, since the confirmation can only be made by the non-SAP system. You do not process workflow work items for notes from the inbox as you do for errors, but rather complete the workflow work item.

SAP Extended Warehouse Management (SAP EWM)

510

482

SAP Online Help

20.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] , so that you can adapt and enhance the interface processing to meet your requirements.

SAP Extended Warehouse Management (SAP EWM)

510

483

SAP Online Help

20.07.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. You create a user-defined processing module, which you copy from the standard function module for the respective message type and adjust accordingly.

●

You use the standard IDoc but want to adjust the standard IDoc processing. That is to say, you want to modify error processing or want to interpret the contents of the IDocs to suit your individual needs. You implement the Business Add-In (BAdI) in the standard function module: ○

If you want to influence error processing, you implement the BAdI /SCWM/WMIDOC with the method Error_Inbound.

○

If you want to influence IDoc processing, 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, see BAdI Methods for the Interface [Seite 489]. ●

You use a modified IDoc with user-defined segments and want to execute a particular process for the data from these segments. In the standard IDoc, 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 modified IDoc with customized segments and want to define IDoc processing yourself. You define customized IDoc segments in the standard IDoc and create a customized processing function module.

●

You use a user-defined IDoc with a new message type and have to implement processing of the IDoc on your own. You define a user-defined IDoc and create a user-defined processing function module. When you create the function module, you can use the standard auxiliary function modules.

Features Adjusting the Standard Function Module As soon as the SAP system has received the IDoc and saved it, the system calls a main function module of the application, which takes over the processing of the IDoc.

SAP Extended Warehouse Management (SAP EWM)

510

484

SAP Online Help

20.07.2007

At this point, you have the first opportunity to intervene in the IDoc processing, by creating a user-defined function module. 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. There, 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. Main function modules for inbound IDoc processing Message type

Function module

Use

/SCWM/WMBBIN

/SCWM/IDOC_INPUT_WMBBIN

Block storage bins

/SCWM/WMCATO

/SCWM/IDOC_INPUT_WMCATO

Cancel TW

/SCWM/WMSUMO

/SCWM/IDOC_INPUT_WMSUMO

Move Handling Unit

/SCWM/WMTOCO

/SCWM/IDOC_INPUT_WMTOCO

Confirm TW

/SCWM/WMTORD

/SCWM/IDOC_INPUT_WMTORD_MULTIPLE

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.

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.

●

You can use the BAdI method before the function module call, for example, to perform your own updates or to evaluate your own segments (that you have added in the IDoc definition).

You can find the name of the BAdI method in the source code for the main function module. If you create your own function module or BAdIs, make sure that you do not set any COMMIT WORK statements, as these can cause errors during IDoc processing and inconsistencies during error processing. The system returns to the ALE layer following processing, where the system updates any application errors that have occured, sets the IDoc status, and may even execute database rollbacks.

Note that additional I/Os in the BAdIs can reduce performance.

Defining User-Defined IDoc Segments You define your own IDoc segments from the SAP Easy Access screen, by choosing Tools → ALE → ALE Development → IDoc → IDoc Type Development → IDoc Types. For more information, see Segment Editor [Extern].

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

SAP Online Help

20.07.2007

/SCWM/IDOC_CREATED_OBJECTS_SAVE

Continuously save the documents created from an IDoc

/SCWM/IDOC_ERROR_SAVE

Continuously save IDocs with errors

/SCWM/IDOC_INPUT_REFRESH

Initialization for IDoc processing (table refresh)

/SCWM/IDOC_OK_SAVE

Continuously save processed IDocs

/SCWM/IDOC_RETURN_CREATE

Determine and construct status record for the IDoc

/SCWM/IDOC_ROLLBACK_SAVE

Update IDoc tables after necessary rollback

/SCWM/IDOC_STATUS_CREATE

Determine and construct status record for the IDoc

/SCWM/IDOC_TIDOC_FETCH

Fetch internal table for the purpose of status update

Defining User-Defined IDocs If you define your own IDocs (intermediate structure), you assign this IDoc to a new message type. To do this, on the SAP Easy Access screen, choose Tools → ALE → ALE Development → IDoc IDoc Type Development → IDoc Types. For more information, see Defining New IDoc Types [Extern]. You create a partner profile for this message type. You define the tables for inbound processing for this IDoc under Tools → ALE → ALE Development → IDoc → Inbound Processing. Standard task TS00008099 is available for error processing.

SAP Extended Warehouse Management (SAP EWM)

510

486

SAP Online Help

20.07.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. You create a user-defined processing module, 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 use the standard IDoc, but want to specify when and to whom the system should send a warehouse task item. In this case, you do not use the standard flow of the interface. You realize your own connection for the interface between Extended Warehouse Management (EWM) and the non-SAP system.

●

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 define your own IDoc segments and use the BAdI method to enter data into your own segments.

●

You use a modified IDoc with user-defined segments and want to implement IDoc construction yourself. You define your own IDoc segments in the standard IDoc and create your own processing function module, which you copy from the standard function module of the relevant message type and adjust accordingly.

●

You use a modified IDoc with user-defined segments and do not want to use the standard flow of the interface. In the standard IDoc, you define your own IDoc segments and realize your own connection for the interface between EWM and the non-SAP system.

●

You use an individually defined IDoc with a new message type and have to implement IDoc construction yourself. You define an individual IDoc and create an individually defined function module. Standard auxiliary function modules are available for this purpose.

●

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, and realize your own connection for the interface between EWM and the non-SAP system.

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, determines the partner (the connected system), and steers towards the ALE layer for further processing. At this point, you have the first opportunity to intervene in the IDoc processing, by creating a user-defined function module.

SAP Extended Warehouse Management (SAP EWM)

510

487

SAP Online Help

20.07.2007

You enter this function module in Customizing for Extended Warehouse Management under Interfaces → Non-SAP Systems → Connect Subsystem. EWM uses the following function modules to construct and send IDocs: Function modules for outbound IDoc processing Function module

Name

/SCWM/IDOC_CREATE_WMTOID01

Warehouse tasks

/SCWM/IDOC_CREATE_WMRRID01

Group release

/SCWM/IDOC_CREATE_WMCAID01

Cancellation request WT

In the function modules, you can use BAdI methods to add your own IDoc segments, or to influence the structure of the standard IDoc.

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, and to which non-SAP system you want to send the data.

In this case, the interface must not be active in EWM. You use the BAdI method BAdI. WT Confirmation, to realize your own connection between the systems.

Defining User-Defined IDoc Segments You define your own IDoc segments from the SAP Easy Access screen, by choosing Tools → ALE → ALE Development → IDoc → IDoc Type Development → IDoc Types. For more information, see Segment Editor [Extern].

Defining User-Defined IDocs If you define your own IDocs (intermediate structure), you assign this IDoc to a new message type. To do this, on the SAP Easy Access screen, choose Tools → ALE → ALE Development → IDoc IDoc Type Development → IDoc Types. For more information, see Defining New IDoc Types [Extern]. You create a partner profile for this message type.

SAP Extended Warehouse Management (SAP EWM)

510

488

SAP Online Help

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

Name

ERROR_INBOUND

Error processing in Idoc inbound for IDocs: /SCWM/WMTOCO, /SCWM/WMCATO, /SCWM/WMBBIN, and /SCWM/WMSUMO jointly

WMTOCO_INBOUND

Message /SCWM/WMTOCO (confirm warehouse task) inbound

WMCATO_INBOUND

Message /SCWM/WMCATO (cancel warehouse task) inbound

WMBBIN_INBOUND

Message /SCWM/WMBBIN (block storage bin) inbound

WMSUMO_INBOUND

Message /SCWM/WMSUMO (move handling unit) inbound

WMTORD_OUTBOUND

IDoc /SCWM/WMTOID01 (warehouse task) outbound

WMCATO_OUTBOUND

IDoc /SCWM/WMCAID01 (cancellation request for warehouse task) outbound

WMREF_OUTBOUND

IDoc /SCWM/WMRRID1 (release wave) outbound

WMTORD_INBOUND

Message /SCWM/WMTORD (create warehouse task) inbound

SAP Extended Warehouse Management (SAP EWM)

510

489

SAP Online Help

20.07.2007

Handling Unit (HU) Definition A handling unit is a physical unit consisting of packaging materials (load carriers/packing material) and the goods contained on/in it. A handling unit is always a combination of products and packaging materials [Seite 492]. All the information contained in the product items, for example, about batches, is retained in the handling units and is always available. Handling units can be nested, and you can create a new handling unit from several other handling units. A handling unit has a unique, scannable identification number that you can construct according to industry standards such as EAN 128 or SSCC. Pallet = HU 110

Pallet = HU 120

Package HU 111

Package HU 121

©

SAP AG

Package HU 112

Filename

Container = HU 100

Package HU 122

Date/ 1

Fig. 1: Example of a Handling Unit

Structure The object ‘Handling Unit’ contains the following attributes: ●

Identification number

●

Dimension

●

Weight

●

Volume

●

Status

●

Products and quantities

●

Packaging material

●

Packaging specification

A handling unit consists of a handling unit header and handling unit items. It receives a unique number that is used for identification purposes.

Handling Unit Header The header data of a handling unit is divided up as follows: ●

Weight/volume/dimension

●

General data

●

Storage-specific data

SAP Extended Warehouse Management (SAP EWM)

510

490

SAP Online Help

20.07.2007

For more information about the different detailed information, see Packing at the Work Center [Seite 506].

Status The handling unit is connected to general status management. This enables you to document the various physical statuses (such as planned or realized) and other attributes (such as, weighed, loaded, blocked, or posted for GI) for a handling unit. If you want to use your own status, you can store a user schema for the packaging material type.

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

SAP Extended Warehouse Management (SAP EWM)

510

491

SAP Online Help

20.07.2007

Packaging Materials Definition Packaging materials are used to enclose or hold together the packaged goods. You can pack the packaged goods into or onto the packaging material. The packaging material can be a load carrier. The most important packaging materials are, for example, crates, boxes, containers, wire baskets, and pallets. Box

Cont ainer

Wire box

Crat e

Pallet

Truck

Use For each packaging material that you want to use, you must maintain product master data. The gross weight and the volume that you enter in the product master are particularly important for packing. If you create a handling unit, the master data for the packaging material is automatically adopted, and the gross weight and volume become the tare weight and/or tare volume of the handling unit.

The tare weight and tare volume refer to the gross weight and volume of the packaging material. In the case of a container, for example, this is the tare weight of the unloaded container (the total weight of the container minus any goods and packaging materials packed into it).

Structure If you choose the Global Data view in the product master record, you can maintain the following data in the Packing Data screen section (you access product maintenance from the SAP menu. To do this, 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

SAP Online Help ●

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

Integration Packaging materials are a special type of product that can be used for packing or transporting goods. 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.07.2007

Packaging Specification Definition A packaging specification is master data. The packaging specification defines all the necessary packing levels for a product in order, for example, to put away or transport the product. For a product, a packaging specification mainly describes in which quantities you can pack the product into which packaging materials in which sequence.

Use ●

In printed form, a packaging specification is a set of instructions for the employee in the warehouse. More specifically, the work steps that you enter in a packaging specification are intended as information for the employee. In this way you can, for example, give the employee exact instructions as to where to place the label on a box, or how a product should be stacked onto a pallet.

●

The system can determine packaging specifications during various processes (see below). Processes that determine packaging specifications use only parts or specific attributes from the packaging specification.

Structure Header

Product

Contents

OR or

Packaging specification Level 1

●

EG 1

Element 1

Pack. mat.

Work step

Element 2

Pack. mat.

Work step

Level 2

EG 2

Element 1

Pack. mat.

Work step

Level n

EG n

Element 1

Pack. mat.

Work step

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

SAP Extended Warehouse Management (SAP EWM)

510

494

SAP Online Help ●

20.07.2007

Contents A packaging specification contains a product. However, some packaging specifications contain more than one product, or refer to other packaging specifications.

●

Level You can map various packing levels in a packaging specification. Each level contains a target quantity, which defines how many times you can pack the previous level into this level.

●

Element group For each level there is exactly one element group. However, you can reuse element groups in several packaging specifications.

●

Elements Elements consist of a packaging material and/or a work step.

●

Step A text with an identification, which you can use in one or more packaging specifications.

●

Packaging material A product that is defined with a packaging material type in the product master.

Example for a Packaging Specification and Its Structure: Header: Name: PS1, Status: New Contents: product A, 1 piece Level 1: Target quantity one, element group EG1 Element group EG1: ●

Element E1: packaging material ‘Small box’, work step ‘Place 1 piece upright in each box’

●

Element E2: additional packaging material ‘Label’, work step ‘Place label on upper left’

Level 2: Target quantity 50, shift quantity 10, element group EG2 Element group EG2: ●

Element E3: packaging material ‘Pallet’, work step ‘Place boxes layer by layer onto pallet’

Integration The following figure shows which processes use the packaging specification, and using which components:

SAP Extended Warehouse Management (SAP EWM)

510

495

SAP Online Help

20.07.2007

Processes for the Packaging Specification

Inb. delivery/ASN

Putaway-WT Stock-removal-WT Slotting

Automatic packing

Palletization

ICH

Whse-int. processes

Pick-HU proposal

ATP sourcing

Warehouse order

EWM

MM deployment

Rounding rules

APO

Packaging Specification iPPE

Cond. technique

In both the Inventory Collaboration Hub (ICH) and in Extended Warehouse Management (EWM), you can use the same packaging specification for an inbound delivery or an ASN that you then use for the Automatic Packing [Seite 510] process.

Example Palletization data in EWM In your warehouse, you put away product A onto pallets for 50 pieces. Create a packaging specification with a level that contains the main packaging material Pallet and the contents Product A. For this level, enter the target quantity 50. In the process ‘Putaway’ for the inbound delivery, the system splits the quantity in the inbound delivery across multiple warehouse tasks, due to this packaging specification. For example, if a quantity of 100 pieces is delivered, then the system creates two warehouse tasks for 50 pieces.

Functions of the Packaging Specification The following functions are possible for packaging specifications: ●

Create, copy, and activate (see also: Creation of Packaging Specifications [Seite 497])

●

Determine (see also: Packaging Specification Determination [Seite 499])

●

in mehrere Systeme verteilen.

SAP Extended Warehouse Management (SAP EWM)

510

496

SAP Online Help

20.07.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. For more information, see the Implementation Guide (IMG) for SCM Basis under Packing → Packaging Specification.

Features When you access the Maintain Packaging Specification transaction, the overview screen appears first. This is divided into two parts: the upper screen is used to search for existing packaging specifications. The lower screen is a list in which you create new packaging specifications, and can display or change existing packaging specifications. From the list, you can go to the create, change, and display functions on the detail screen. This displays the structure of the packaging specification in the left screen area (in other words, the levels, elements, and the contents). The upper right screen area shows the most important header data for the packaging specification. The lower right screen area shows the detail data for the selected subobject of the packaging specification (in other words, for the level, the element, or the contents).

Activities ...

1. On the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Packaging Specification → Maintain Packaging Specification. 2. The overview screen appears. Here you can access existing packaging specifications using the quick search or the advanced search. 3. To create a new packaging specification, choose Add New Line (symbol

).

4. In the PS Group column, select a packaging specification. 5. Select the packaging specification, then choose Change to access the detail screen. 6. On the detail screen, you can first edit the header attributes for packaging specification, for example, you can enter a description or define the business key for the packaging specification (Determination tab page). 7. 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). If you work without level sets, then you should specify the structure of the specification in the packaging specification. You create levels and contents in the left screen area using the context menu (right mouse button). 8. When you create a packaging specification that describes the packing for a product, you enter the product in the Contents area.

SAP Extended Warehouse Management (SAP EWM)

510

497

SAP Online Help

20.07.2007

9. For a level, you enter a target quantity and, where required, the minimum and layer quantity. Note that these quantities refer to the previous levels. Target quantity 10 for level 2 means, for example, that you should pack level 1 ten times into the main packaging material for level 2. In other words, 10 boxes onto one pallet. 10. For a level, you can either create the elements manually, or if you are working with a level set then the elements are proposed by the system. 11. To specify the main packaging material for a level, for example, create an element with HU relevance Main Packaging Material, and enter the packaging material in the relevant field. 12. The attributes Weight, Volume, and Dimensions (tab page) for the level are automatically determined by the system for the first main packaging material for a level. For this, the system adopts the attributes for tare and maximum weight (and/or volume, and/or capacity) and the dimensions from the product master for the packaging material. Choose HU Check to make the system calculate the attributes Loading and Total Weight (and/or Volume, and/or Capacity). 13. When you save, you close a packaging specification in the detail area. 14. Choose Back (F3) to go back to the overview area. 15. In the overview area, you can activate one or more packaging specifications. 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]). If the packaging specification contains all the data and you can use the packaging specification for the process, then you activate the packaging specification. 16. The overview area also offers you the functions Copy, New Version, Print Preview, and Delete.

SAP Extended Warehouse Management (SAP EWM)

510

498

SAP Online Help

20.07.2007

Packaging Specification Determination Use You can use this function to determine a packaging specification using the business characteristics you have defined. The system uses the condition technique to do this. From the business characteristics predefined by SAP, you select those that are suitable for your processes (for example, product and vendor). A set of business characteristics forms a condition type. You can define different condition types for different processes. After you have specified a condition type, you can assign a packaging specification to these business characteristics. This means that you can, for example, specify that for a product P, vendor A, and process Automatic Packing in the Inbound Delivery, the system finds packaging specification PS. At the end of this process, handling units are created on the basis of the packaging specification found.

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

●

In the SAP standard system, Customizing settings for packaging specification determination have been predefined. However, you can make enhancements in the customer namespace. For packaging specification determination, you require the following:

●

○

Condition table

○

Access sequence

○

Condition type

○

Determination procedure

You have created, specified, and activated determination records for a packaging specification.

SAP Extended Warehouse Management (SAP EWM)

510

499

SAP Online Help

20.07.2007

Features For more information about condition technique, see the CA documentation for message control. Packaging specification determination runs using the same principles.

Activities The following describes how to create determination records in the system: ...

1. Choose Extended Warehouse Management → Master Data → Packaging Specification → Maintain Packaging Specification. The Packaging Specification Overview screen appears. 2. Choose a packaging specification that already exists, or create a new specification, and choose Change (if you have already activated the selected packaging specification, you must first create a new version of this packaging specification). 3. On the determination tab page (Details for PS Header), enter a condition type or use the proposed condition type (see Customizing Define Level Set). This screen always displays all condition records that you have created for the packaging specification. 4. 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, perform this activity). You can configure these combinations as you want using Customizing. Choose OK. 5. Depending on the condition table/key combination you selected, make the mandatory entries (the current packaging specification number is entered automatically in the column). If necessary, change the sequence number of the condition record, to change the sequence of the determination. If, for example, you selected the key combination supply chain unit/product, then the subsequent mandatory entries are the supply chain unit and the product. If the system shows you condition records for other packaging specifications, then any condition record that is also displayed has the same key combination as the newly created record. Check whether there is an overlap of the two keys. 6. Save your condition record. 7. If there are no active packaging specifications, then you activate the packaging specification. If there is an active version of the packaging specification, then the condition records refer to the packaging specification number (regardless of the version), and the system takes this packaging specification into account during packaging specification determination. 8. You can use the Condition Maintenance transaction for activated packaging specifications, to add new condition records, or to change/delete existing records. Here you can also see an overview of all condition records, without reference to specific packaging specifications.

If the semantic key (in other words, the condition table, all fields of the condition table, and the condition sequence) are the same within a validity period, this results in an overlap of two condition records. 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 you can activate a packaging specification. If at least one condition record for the active packaging specification contains an error (in other words, will not be included in the determination), or if no condition record exists for this packaging specification, a yellow traffic light is displayed in the packaging specification overview.

SAP Extended Warehouse Management (SAP EWM)

510

500

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

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

●

Handling units (displayed as symbol

●

Storage section (displayed as

●

Open warehouse task (displayed as

symbol) symbol) or

, with or without system lock)

symbol) symbol)

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

SAP Extended Warehouse Management (SAP EWM)

510

507

SAP Online Help Quality inspections

o ●

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

Description

Smart Form

HU_CONTENT

Print HU contents document with serial numbers

/SCWM/HU_CONTENT

HU_EXPRESS

/SCWM/HU_EXPRESS

HU_HAZARD

Print hazardous goods label

/SCWM/HU_HAZARD

HU_LABEL

Print HU label

/SCWM/HU_LABEL

HU_SHPLABEL

Print shipping label

/SCWM/HU_SHPLABEL

HU_TO

Print HU warehouse tasks

/SCWM/HU_TO

HU_SERIAL

Print HU serial number label

/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

WT Number

CFG1

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

Final Storage Bins JK01, JK02, JK03

Packing Station WS20

SID1 SID2 SID3

SID1 SID2 SID3

SID1 SID2 SID3

SID1 SID2 SID3

SID1 SID2 SID3

HU2

HU2

HU2

HU1

HU1

Warehouse SPU2

Deconsolidiation Station DS10 SID1 SID3

GR Zone GR10

SID1 SID2 SID3

SID1 SID2 SID3

SID1 SID2 SID3

HU2

HU2

HU2

Final Storage Bins JK01, JK02, JK03

HU3

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

SAP Online Help

20.07.2007

data Warehouse Number and Work Center and choose Execute. Scan the stock identification of the products, that is, the labels located within the HU. Go to the Stock Details tab page. EWM uses the stock identifications to find the corresponding stock and displays the respective stock attributes, such as product name or quantity. If you want to enter count results, choose the stock using the stock identification. Enter the count results on the Counting tab page. If you want to enter quality inspection results, such as findings or decisions, choose the stock using the stock identification. Go to the Q-Inspection tab page and enter the inspection results. ●

In user interfaces that support radio frequency, you can use stock identification for the following process steps: ○

Deconsolidation

○

Packing

○

Counting

○

Putaway

To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → /SCWM/RFUI - Log On to RF Environment. When you log on to the RF environment, you can work with stock identification in the following logical transactions only. ○

For deconsolidation, choose 03 Goods Receipt Processes → 02 Deconsolidation → 04 Deconsolidate Automatically or 05 Deconsolidate Manually

○

For packing, choose 04 Goods Issue Process → 02 Packing → 04 Repack HU Item Automatically or 07 Repack HU Item Manually

○

During counting, choose 05 Internal Processes → 04 Quality Management → 04 QM Counting → 03 QM Counting Results manually

○

For putaway, choose 03 Goods Receipt Processes → 03 Putaway → 01 Putaway by HU, 02 Putaway by HU (Clustered), 03 Putaway by Warehouse Order or 04 Confirmation Correction

See Also: Work Processing Using Radio Frequency [Seite 797]. In the warehouse management monitor, you can search for WTs for the stock identification and for stocks for the stock identification. For example, on the SAP Easy Acces Screen, choose Extended Warehouse Management → Monitoring → Warehouse Management Monitor. On this screen, choose Documents → Warehouse Task in the navigation tree. Specify a stock identification in the Stock Identification field in the Warehouse Task screen area.

If you work with stock identification, 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). This allows EWM to carry out faster search queries.

SAP Extended Warehouse Management (SAP EWM)

510

522

SAP Online Help

20.07.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). Here, Extended Warehouse Management (EWM) creates WTs with new stock identifications. You can print labels showing the new stock identifications.

Prerequisites See Stock Identification in the GR and GI Processes [Seite 518] and Using Stock Identification [Seite 521].

Process

WT No. 1001 / 001 … Product XYZ 6 Pieces Stock ID ANDI 9898

1001

Label

WT No. 1001 … Product XYZ 10 Pieces Stock ID ANDI

Stock ID:

Label

Stock ID:

When you confirm a WT with a partial quantity, a WT split occurs. EWM assigns a new stock identification to the split quantity. The following figure provides an overview of the use of stock identification when splitting a WT in the GR and GI processes.

WT No. 1001 / 002 … Product XYZ 4 Pieces Stock ID ANDI 1001

...

1. You have packed stock into a handling unit (HU), for example, HU1. 2. You only confirm part of the stock in the corresponding WT. For example, only six pieces fit into HU1 instead of the required ten. a. You only confirm six pieces in the WT, for example WT 1001/001, . b. Depending on your Customizing settings, EWM splits the WT and creates a new WT (such as 1001/002) with four pieces for the remaining quantity. c. EWM assigns a new stock identification (such as AND198898) to the confirmed WT. This means that the two different stocks have two separate stock identifications to ensure unique stock identification.

EWM only retains the same stock identification as in the original WT for the WT that was confirmed last. 3. You confirm WT 1001/002. 4. You print new labels for both stock identifications and apply them.

SAP Extended Warehouse Management (SAP EWM)

510

523

SAP Online Help

20.07.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. Here, Extended Warehouse Management (EWM) creates new putaway warehouse tasks (putaway WTs) with new stock identifications. For example, you receive a handling unit (HU) from a supplier, the contents of which has one stock identification. You want to put this HU away and you determine that this requires two destination storage bins.

Prerequisites See Stock Identification in the GR and GI Processes [Seite 518] and Using Stock Identification [Seite 521].

Process The following figure provides an overview of the use of stock identification when splitting stock in the GR process. … Product XYZ 10 Pieces Stock ID ANDI

WT No. 4711 … Product XYZ 6 Pieces Stock ID ANDI 1001 Target Stock ID SPU24711

1001

WT No. 4712 … Product XYZ 4 Pieces Stock ID ANDI 1001 Target Stock ID SPU24712

...

1. You receive an inbound delivery with an HU. For example, you receive an HU1 with ten pieces. 2. EWM creates the required putaway WTs in accordance with the putaway strategy, for example, putaway WT 4711 with six pieces and putaway WT 4712 with four pieces. If you do not confirm the putaway WTs immediately, both of them receive the available stock identification, for example, the stock identification ANDI1001 and a new target stock identification each, such as SPU24711 and SPU24712. 3. If you want to search for putaway WTs for a stock, you use the stock identification to search for the unconfirmed putaway WTs for a stock. EWM then displays all the corresponding, open putaway WTs. For example, you use the stock identification ANDI1001 to search for the corresponding putaway WTs. EWM displays the putaway WTs 4711 and 4712 as the result. 4. When you confirm the putaway WT during deconsolidation for example, you can still specify or scan the stock identification ANDI1001 that was printed on the original label. EWM then displays the options WT 4711 and WT 4712. You choose one WT and confirm it. EWM then transfers the target stock identification to the stock. If you have not done so already, you must now print new labels with the new stock identifications and apply them.

SAP Extended Warehouse Management (SAP EWM)

510

524

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

525

SAP Online Help

20.07.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). Here, Extended Warehouse Management (EWM) creates new warehouse tasks (WTs) with new stock identifications. You can print labels showing the new stock identifications.

Prerequisites See Stock Identification in the GR and GI Processes [Seite 518] and Using Stock Identification [Seite 521].

Process The process flow for using stock identification corresponds with the process flow for splitting WTs, in other words, 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.

WT No. 2002 … Product XYZ 4 Pieces Stock ID ANDI

9898I

1001

Label

… Product XYZ 10 Pieces Stock ID ANDI

Stock ID:

Label

Stock ID:

The following figure provides an overview of the use of stock identification when splitting stock in the GI process.

WT No. 3003 … Product XYZ 6 Pieces Stock ID ANDI

1001

...

1. If, while you are repacking products you realize that instead of being able to pack ten pieces of a product in an HU (HU1, for example) you are only able to pack four pieces for example, you must carry out a stock split. You can carry out the stock split during repacking, thereby repacking with WTs that have been confirmed immediately. 2. You reduce the default quantity from ten pieces to four pieces. 3. For repacking, EWM creates an immediately confirmed WT (2002, for example) with a new stock identification (AND19898, for example) with the partial quantity of four pieces. 4. For repacking, EWM also creates an immediately confirmed WT (3003, for example) with the remaining quantity of six pieces with the original stock identification (ANDI1001, for example). This ensures unique stock identification. 5. You print new labels for both stock identifications and apply them.

SAP Extended Warehouse Management (SAP EWM)

510

526

SAP Online Help

20.07.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, and to document them. Typical VAS activities are assembling products, packing products, labeling, or kitting [Extern]. Here, both the goods receipt process and the goods issue process in the warehouse change. In an ideal case, you can then use process-oriented storage control to execute interim steps before final putaway or before staging in the goods issue area. In these interim steps, the VAS order defines which product processing must be performed by warehouse employees in the work centers, for example. You can also use a VAS order in the goods issue process to assemble kits for your customers, and to pack them on a customer-specific basis using this VAS order.

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, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Value-Added Services (VAS).

Integration Value-added services are integrated into EWM and the delivery.

Features You have created an inbound or outbound delivery, 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] ...

●

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

SAP Online Help

20.07.2007

VAS Order Definition Instruction to perform a value-added service (VAS) for one or more products with reference to a delivery item. A value-added service order (VAS order) links delivery items to a packing instruction and contains details from within the delivery and packaging specification.

Use A VAS order is a document with which you can inform warehouse employees about what work they have to perform, and with which products. You can also use VAS orders to log work that is done. 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. The delivery tells the VAS order about the exact amount of work to be performed. You can use the data collected in the VAS order as a calculation basis for billing external and internal service providers, for example.

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. Here, 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]).

Example You have an inbound delivery with one item for 10 pistons, which you want to prepare for final putaway. The system finds a packaging specification with the following activities for the product in goods receipt: 1. Protect piston from rust 2. Paint piston yellow 3. 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 order now looks like this: ●

The packaging specification is stored in the order header.

●

The VAS activities include the three activities Protect from rust, Paint yellow, and Pack.

●

The items contain quantity 10 and product Piston.

●

The rust protection material, yellow paint, and box are listed in the auxiliary products.

SAP Extended Warehouse Management (SAP EWM)

510

528

SAP Online Help

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

Goods Receipt Process with VAS Order Purpose The goods receipt process [Seite 263] changes when used in connection with value-added services. You can perform the required VAS activities for a VAS order at special work centers in an interim step, before you complete the final putaway for the products.

Prerequisites An inbound delivery exists, as does a valid packaging specification, meaning that the system can create a VAS order. 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, you must have already configured process-oriented storage control in Customizing for value-added services (see: Process-Oriented Storage Control [Seite 336]).

Process Depending on how you use storage control, the following options are available to you in the goods receipt process for performing value-added services using a VAS order: ...

●

You are using process-oriented storage control: a. The system creates a VAS order based on the inbound delivery. b. For each inbound delivery item, the system determines the corresponding packaging specification. c. The system then creates handling unit warehouse tasks that contain a work center as the destination storage location in accordance with the VAS order. Here, each VAS activity represents a separate process step with a corresponding warehouse task. You can define as many interim steps for the products as you require. All of these interim steps are of the type VAS possible. d. After completing all value-added services, the system puts away the products in the final storage bin.

●

You have only defined the individual process steps, and are not using process-oriented storage control:

...

a. The system creates a VAS order based on the inbound delivery. b. For each inbound delivery item, the system determines the corresponding packaging specification. c. The system then creates product warehouse tasks that contain a work center as the destination storage location in accordance with the VAS order. Here, each VAS activity represents a separate process step. You can define as many interim steps for the products as you require. d. After completing all value-added services, the system puts away the products in the final storage bin. ●

You are not using process-oriented storage control, and you have not defined any process steps:

...

a. The system creates a VAS order based on the inbound delivery. b. For each inbound delivery item, the system determines the corresponding packaging specification. c. You print out the VAS order and the warehouse employees undertake the VAS activities at the work centers manually.

SAP Extended Warehouse Management (SAP EWM)

510

530

SAP Online Help

20.07.2007

d. As soon as the VAS activities are completed, you can enter a confirmation in the system. The system then puts away the products in the final storage bin. 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

Final putaway bin

HU warehouse task

VAS work center: Painting

VAS work center: Packing

Result The products are prepared for putaway following your requirements, and are put away.

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. The system maps the packaging specification levels in the VAS order as VAS activities.

SAP Extended Warehouse Management (SAP EWM)

510

531

SAP Online Help

20.07.2007

VAS in Goods Receipt Truck

Goods receiving area

Inb. Del. X Item 10: Pyramid 3 pc

Pack. Specification PS1 Content: Pyramid Level 1: Paint blue Level 2: Pack in case

Work center WC01 Painting

Work center WC02 Packing

VAS Order VO1 Activity 1: Work center WC01 VAS item: Pyramid, 3 pc Aux. product: Blue paint Activity 2: Work center WC02 VAS item.: Pyramid 3 pc Aux. product: Case 3 pc

Final storage bin

SAP Extended Warehouse Management (SAP EWM)

510

532

SAP Online Help

20.07.2007

Goods Issue Process with VAS Order Purpose The goods issue process [Seite 314] changes when used in connection with value-added services. You can perform the required VAS activities for a VAS order at special work centers in an interim step, before shipping the products to your customers. You can use this process to pack products for your customers on a customer-specific basis, for example. In goods issue, you can also use the VAS order to assemble kits at the work centers (see Kit to Order [Seite 349]).

Prerequisites An outbound delivery exists, as does a valid packaging specification, meaning that the system can create a VAS order. 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, you must have already configured process-oriented storage control in Customizing for value-added services (see also: Process-Oriented Storage Control [Seite 336]).

Process Depending on how you use storage control, the following options are available to you in the goods issue process for performing value-added services using a VAS order: ...

●

You are using process-oriented storage control: a. The system creates a VAS order based on the outbound delivery. b. For each outbound delivery item, the system determines the corresponding packaging specification. c. The system then creates handling unit warehouse tasks that contain a work center as the destination storage location in accordance with the VAS order. Here, each VAS activity represents a separate process step with a corresponding warehouse task. You can define as many interim steps for the products as you require. All of these interim steps are of the type VAS possible. d. After completing all value-added services, the products reach the goods issue area.

●

You have only defined the individual process steps, and are not using process-oriented storage control:

...

a. The system creates a VAS order based on the outbound delivery. b. For each outbound delivery item, the system determines the corresponding packaging specification. c. The system then creates product warehouse tasks that contain a work center as the destination storage location in accordance with the VAS order. Here, each VAS activity represents a separate process step with a corresponding warehouse task. You can define as many interim steps for the products as you require. d. After completing all value-added services, the products reach the goods issue area. ●

You are not using process-oriented storage control, and you have not defined any process steps:

...

a. The system creates a VAS order based on the outbound delivery.

SAP Extended Warehouse Management (SAP EWM)

510

533

SAP Online Help

20.07.2007

b. For each outbound delivery item, the system determines the corresponding packaging specification. c. You print out the VAS order and the warehouse employees undertake the VAS activities in the work centers manually. d. As soon as the VAS activities are completed, you can enter a confirmation in the system. The products then reach the goods issue area. ●

You are using the VAS order for kitting.

...

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

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. In the following example, the system determines the same packaging specification for

SAP Extended Warehouse Management (SAP EWM)

510

534

SAP Online Help

20.07.2007

the delivery items. The system therefore creates one VAS order only. The system maps the packaging specification levels in the VAS order as VAS activities.

VAS in Goods Issue Pick-HUs Outb. Delivery Z Item.:10: Cycle 3 pc Item.:20: Pump 3 pc

Work Center: Customer-Specific Packing

Loading

SAP Extended Warehouse Management (SAP EWM)

Pack. Spec. PS3 Content: Cycle 1 pc Pump 1 pc Level 1: Gift wrapping Pack. Spec. PS3 Content: Cycle 1 pc Pump 1 pc Level 1: Gift wrapping

VAS Order VO3 Activity 1: Work center CUST VAS item.: cycle, 3 pc VAS item.: pump, 3 pc VAS aux. prod.: case, 3 pc VAS aux. prod.: gift wrap paper

510

535

SAP Online Help

20.07.2007

Create and Edit VAS Orders Use If, for example, your supplier ships products to you packaged, however you notice in the goods receipt area that the products are not packaged, you can use this function to create VAS orders [Seite 528] manually. If you notice that a VAS order does not have a work center, for example, you can also use this function to change this data. You can also use this function to print out VAS orders again and to delete VAS orders.

Integration If you want to implement VAS orders using process-oriented storage control [Seite 336], see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Value-Added Services (VAS) → VAS Integration with Storage Control.

Prerequisites An inbound delivery or outbound delivery exists. A corresponding packaging specification exists (see also: Packaging Specification [Seite 494]). If you want to implement automatic packaging specification determination, you have already specified a determination procedure for packaging specifications in Customizing. For more information, see the IMG for Extended Warehouse Management under Cross-Process Settings → Value-Added Services (VAS) → Define Relevance for VAS.

Activities ...

1. Depending on whether you want to create and manage VAS orders in the goods issue or goods receipt process, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Value-Added Services (VAS) and either: ○

VAS in Goods Receipt Process

○

VAS in Goods Issue Process

2. Enter the warehouse number.

Create VAS Order ...

1. If you want to create VAS orders, choose Goto → Create VAS. 2. Enter the delivery in the Warehouse Request field, and enter the item in the Item Number field. If you leave the Packaging Specification field empty, the system attempts to find a suitable packaging specification. 3. Choose VAS Order → Save.

The system creates a VAS activity in the VAS order for each level of the packaging specification. However, if you have restricted the performing entity in the Entity field, the system only writes packaging specification levels as VAS activities into the VAS order that are also provided for this entity. To find the Entity in the packaging specification, double-click the level and then choose the Warehouse tab page.

SAP Extended Warehouse Management (SAP EWM)

510

536

SAP Online Help

20.07.2007

Change VAS Order ...

1. Enter either the VAS order number or the delivery number. 2. Choose Change. You can now change the work center in the VAS order, for example, or the VAS status. You can also display the packaging specification or the delivery.

Delete VAS Order ...

1. Enter either the VAS order number or the delivery number. 2. Choose Delete. The system deletes the VAS order.

Print VAS Order ...

1. Enter either the VAS order number or the delivery number. 2. Choose the PPF Actions tab page. Here you can use the Post-Processing Framework to print the VAS order or manage other print-specific parameters.

SAP Extended Warehouse Management (SAP EWM)

510

537

SAP Online Help

20.07.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. You can also use the same functions as in packing in the work center [Seite 506] for valueadded services (VAS).

Prerequisites You have configured a work center where you can process VAS orders. To do this, you have configured transaction type Execute VAS in Customizing. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Master Data → Work Center → Define Work Center Layout. In this IMG activity, you can also adjust the respective layout of the work center, and therefore configure which tab pages are displayed on your screen. You have assigned a work center layout with the transaction type Execute VAS to the work center. For more information, see the IMG for Extended Warehouse Management (EWM) under Master Data → Work Center → Define Work Center.

Features You can display all VAS orders for further processing for each warehouse number and work center. The work center screen is split up into the following sections: ●

In the upper left section, the stock that also physically exists in the work center is displayed (Stock Section). In this section, you can create new kits, for example (

●

).

In the bottom left section, you can see all the VAS orders that match your selection criteria (VAS Section). For each VAS order, you can see all the VAS activities along with their respective VAS items and VAS auxiliary products.

●

In the upper right 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]). You can also confirm the work progress of the VAS order (at VAS order header level, VAS activity level, VAS item level, and VAS auxiliary product level).

●

In the bottom right section, you can see the following tab pages, depending on your selection: ○

If you double-click the storage bin ( ) in the Stock Section, the system displays all stock that is available in this storage bin. The system also displays detailed data about the storage bin.

○

If you double-click the HU ( ) in the Stock Section, the system displays the weight and dimensions, 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

SAP Online Help ■

20.07.2007

Confirmed WTs with this HU as a source HU

If you are working with consolidation groups, you can also use an additional tab page to display possible destination HUs for repacking. ○

If you double-click the stock item ( the following information:

) in the Stock Section, the system displays

■

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

If you are working with consolidation groups, you can also use an additional tab page to display possible destination HUs for repacking. ○

If you double-click the VAS order header ( ) in the VAS Section, the system displays all VAS order header data, all VAS activities, and additional data for the VAS order header.

○

If you double-click the VAS activity ( ) in the VAS Section, the system displays VAS activity data, all VAS items, and all VAS auxiliary products for this VAS activity.

○

If you double-click the VAS item ( ) in the VAS Section, the system displays specific VAS item data, serial numbers for this delivery item, dangerous goods texts, and delivery texts. On the Serial Number tab page, you can enter the serial numbers for the corresponding delivery item, since a VAS item always refers to one delivery item.

○

If you double-click the VAS auxiliary product ( ) in the VAS Section, the system displays specific data for the VAS auxiliary products.

Changes in the VAS Section do not automatically affect the Stock Section. For this reason, for example, the system does not automatically create an HU when you set the status of the VAS order to Completed.

Activities On the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Create Confirmation for VAS.

Selection Screen The following work center screen is displayed: Entering Value-Added Services. ...

1. Under Organizational Data, enter a warehouse number and the work center for which you want to enter value-added services using VAS orders. 2. The Filter section allows you to restrict the VAS orders even further. If you do not enter any data here, the system displays all the VAS orders with the status Not being processed. The system displays all the VAS orders for the work center you have entered that match your selection criteria.

SAP Extended Warehouse Management (SAP EWM)

510

539

SAP Online Help

20.07.2007

In the Stock Section, only data for the VAS orders you selected is displayed.

Confirm Work Progress for a VAS Activity ...

1. You can double-click the following levels, depending on which level you want to confirm the work progress: ○

VAS order header (

○

VAS activity (

○

VAS item (

○

VAS auxiliary product (

)

) ) )

2. In the Completed Quantity field, enter the quantity that you want to confirm. When confirming VAS auxiliary products, you must enter the quantity in the Quantity of an Auxiliary Product to Be Consumed field. In this case, the consumed quantity is displayed in the Consumed Quantity field for the VAS auxiliary product after saving. 3. The system automatically adjusts the quantities and status for a confirmation as follows: ○

If you confirm using the VAS order header ( ), the system automatically adjusts the quantities of the VAS activity, VAS item, and VAS auxiliary products.

○

If you confirm using the VAS activity ( ), the system automatically adjusts the quantities of the VAS item and VAS auxiliary products.

○

If you set the status of the VAS order to Completed – Without Quantity Variance, the system automatically sets the status of all VAS activities to Completed – Without Quantity Variance.

○

If you set the status of the VAS activity to Completed – Without Quantity Variance, the system automatically sets the status of all previous VAS activities to Completed – Without Quantity Variance.

If the entered quantity represents a quantity increase, the system automatically adjusts the quantities. For example, if you have previously entered a greater quantity at VAS item level than now, the system saves this quantity without automatically adjusting the other levels.

The VAS activity has a warehouse request quantity of 5 pieces. The VAS item has a warehouse request quantity of 10 pieces. The VAS auxiliary product has a warehouse request quantity of 20 pieces. You enter confirmation of 3 pieces at VAS activity level. The system then updates 6 pieces as completed quantity for the VAS item, and 12 pieces as completed quantity for the VAS auxiliary products. However, if you only confirm the VAS item with 6 pieces or the VAS auxiliary products with 12 pieces as completed, the system does not automatically update the VAS activity. If you confirm the VAS item ( ) or the VAS auxiliary products ( ), the system only saves these quantities; it does not automatically adjust the quantities for the VAS activity or VAS order header. This enables you to confirm the corresponding quantities according to the level of detail you require in the confirmation process. 4. Save your entries.

SAP Extended Warehouse Management (SAP EWM)

510

540

SAP Online Help

20.07.2007

Create Kit ...

1. In the Stock Section, select the HUs for which you want to create kits. 2. Choose

Create Kit from the application toolbar.

3. The system checks the components of the HU and uses this to calculate the complete number of kits that can result from them, and creates these kits. The generated kits are displayed below the HU in the tree display when you choose . 4. In the alternative unit of measure field, you can change the number of kits created before saving. 5. Save your entries.

Confirm Using a Keyboard Scanner ...

1. Choose the tab page for the level at which you want to confirm (VAS header, VAS activity, VAS item or VAS auxiliary product). 2. Scan the VAS order for which you want to perform the confirmation. 3. Enter the completed quantity. The system performs the confirmations using the same logic as described under Confirm Work Progress for a VAS Order. 4. Save your entries.

Pack Using a Keyboard Scanner For more information, see Packing at the Work Center [Seite 506].

SAP Extended Warehouse Management (SAP EWM)

510

541

SAP Online Help

20.07.2007

Auxiliary Product Consumption Posting Use For the value-added services performed at the work centers, you can record which auxiliary products you used for particular activities, and in what amounts.

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. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Product → Maintain Warehouse Product. 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. The stock of the auxiliary products is located in this storage bin, and this stock is then also consumed by this storage bin as part of the valueadded services. To assign a storage bin, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Assign Storage Bins for VAS Consumption Posting. You have maintained a packaging specification and have assigned auxiliary packaging materials to the packaging specification levels (such as preservation, packing into individual containers). To create a packaging specification, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Packaging Specification → Maintain Packaging Specification. If you want to use customer-specific movement types in the ERP system, you can define these in Customizing. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Interfaces → ERP Integration → Goods Movements → Define Customer-Specific Movement Types.

Features If you have set the consumption relevance for the required auxiliary products for value-added services, and have assigned a special storage bin for the auxiliary products, you can record consumption of all auxiliary products in the system. 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. However, you can also manually overwrite the quantity determined by the system (such as for unplanned overconsumption or underconsumption). When you save the confirmation, the system performs consumption posting for the auxiliary products. You can also change quantities of auxiliary products that have already been posted. If you enter a negative value for the quantity of auxiliary product being posted, the consumption is reduced and the system increases the stock in the storage bin. If you enter a quantity to be posted additionally, you can increase the consumption at a later time. Posting reduces the auxiliary product stock in Extended Warehouse Management (EWM) and the stock in the connected ERP system. The standard movement types 291 and 292 are used for consumption posting in the ERP system. However, you can also use your own movement types.

SAP Extended Warehouse Management (SAP EWM)

510

542

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

543

SAP Online Help

20.07.2007

Cross-Docking (CD) Purpose If you are aiming to process products and handling units (HUs) as efficiently as possible, and to minimize unnecessary load transfer activities in the warehouse, then you can use this process in a distribution center or warehouse. Reducing the time in storage in the warehouse enables you to reduce stockholding costs. In the case of Transportation Cross-Docking [Seite 547] (TCD), you can also optimize transportation costs. You transport the products or HUs from goods receipt to goods issue without putaway occurring in between. In the case of TCD, you only work with HUs. Using cross-docking enables you, for example, to increase the number of processed HUs and fulfill urgent sales orders, or reduce processing and storage costs. In TCD, you define in Customizing how the cross-docking process (CD process) is to proceed. You work with cross-docking routes [Seite 644] (CD routes). The routing guide uses these CD routes to decide whether a TCD process would be advantageous. In the case of a TCD, the ERP system generates a corresponding delivery pair, that is, an inbound delivery and an outbound delivery that contain the same TCD operation number. The ERP system sends this delivery pair to Extended Warehouse Management (EWM), which executes the TCD process. The CD relevance is therefore defined before stock arrives and before you release the outbound delivery or warehouse task, meaning you perform planned CD. For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Cross-Docking (CD) → Basic Settings for Transportation Cross-Docking (TCD). In the case of push deployment (PD) and pick from goods receipt (PFGR) [Seite 559], 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, meaning you perform unplanned CD. For more information, see the IMG for EWM under Cross-Process Settings → Cross-Docking (CD) → Basic Settings for PD and Pick From GR.

Prerequisites ERP system For a description of the prerequisites in the ERP system, see the SAP Help Portal under mySAP ERP → Logistics → Logistics - General (LO) → Service Parts Management (LOSPM) → Transportation Cross-Docking.

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.

●

You have defined separate warehouse process types where required.

If you want to work more quickly with CD-relevant inbound deliveries, such as searching for CD-relevant inbound deliveries, we recommend that you define separate warehouse process types in Customizing. For more information, see the IMG for EWM under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type. For more information, 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

SAP Online Help

20.07.2007

Prerequisites for TCD: ●

You have defined separate document types for the inbound and outbound deliveries where required.

●

You have performed the corresponding Customizing for Route Determination with the Routing Guide [Seite 638].

For more information, 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. Prerequisites for PD/PFGR: ●

You have defined separate document types for the outbound delivery where required. For more information, 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.

●

You have performed the corresponding Customizing in SAP APO. For more information, see Event-Driven Quantity Assignment [Extern].

Process The following gives you an overview describing the simplest CD process without using storage control. For a detailed process flow description of this overview process, see TCD, Push Deployment and Pick From Goods Receipt. ...

1. You receive an inbound delivery. The routing guide uses the route to decide whether a TCD process is required. If a TCD is required, the ERP system generates a corresponding delivery pair and sends it to EWM. For more information, see the SAP Help Portal under SAP ERP → Logistics → Logistics - General (LO) → Service Parts Management (LO-SPM) → Transportation Cross-Docking. For PD and PFGR, EWM receives the CD information from the ERP system. 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. 2. In this simple case, EWM specifies the destination storage bins, such as the goods issue zone, directly in the outbound delivery. When EWM generates a pick-warehouse task, it determines the destination storage bin from the outbound delivery. Here it uses a warehouse task for cross-docking that updates both the inbound and the outbound delivery. For more information about updating the inbound delivery in cross-docking, see Updating the Inbound Delivery in the GR Process [Seite 271]. The following graphic shows you the simplest instance of cross-docking.

SAP Extended Warehouse Management (SAP EWM)

510

545

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

546

SAP Online Help

20.07.2007

Transportation Cross-Docking (TCD) Purpose Transportation cross-docking [Extern] (TCD) supports the transportation of handling units (HUs) across different distribution centers or warehouses, up to the final place of destination. Examples for this are to switch the means of transport, to consolidate multiple deliveries to new transports, or to process export activities centrally. If the final place of destination is a distribution center or warehouse at the customer site, a sales order in SAP Customer Relationship Management (SAP CRM) forms the basis for TCD. However, you can also use TCD to transport HUs to your own final warehouse. In this case, a stock transfer order forms the basis for TCD.

For more information about the complete process for stock transfer orders in the ERP system, see the SAP Help Portal for SAP ERP under SAP ERP Central Component → Logistics → Logistics - General (LO) → Service Parts Management (LO-SPM) → Transportation Cross-Docking → Process Flow for Stock Transfer Orders. 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 - General (LO) → Service Parts Management (LO-SPM) → Transportation Cross-Docking → Process Flow for Sales Orders. When you pick a TCD-relevant HU, 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. In EWM, 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. The monitor only gives you information about the current process status. However, 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. For more information, see the SAP Help Portal for SAP ERP under SAP ERP Central Component → Logistics → Logistics - General (LO) → Service Parts Management (LO-SPM) → Transportation CrossDocking → Monitor for Transportation Cross-Docking.

Restrictions ●

TCD does not support returns.

●

If you use nested mixed pallets in TCD, a subordinate HU can contain either TCDrelevant delivery items only, or non-TCD-relevant delivery items only.

●

In a supply chain in TCD, only the final place of destination can be located abroad.

Prerequisites ●

You have performed Customizing in the ERP system. For more information, see the SAP Help Portal for SAP ERP under SAP ERP Central Component → Logistics → Logistics - General (LO) → Service Parts Management (LO-SPM) → Transportation Cross-Docking.

●

You have performed Customizing for Route Determination with the Routing Guide [Seite 638] and defined CD routes [Seite 644].

●

As standard procedure, 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. You can deactivate this call for all outbound delivery orders or for outbound

SAP Extended Warehouse Management (SAP EWM)

510

547

SAP Online Help

20.07.2007

deliveries in Customizing for each document type. The check criterion is the existence of a final ship-to party, meaning EWM only calls SAP GTS for a document type if no final ship-to party has been specified. For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Cross-Docking (CD) → Basic Settings for Transportation Cross-Docking. ●

You have defined separate document types and warehouse process types where required.

If you want to work more quickly with TCD-relevant inbound deliveries, such as searching for TCD-relevant inbound deliveries, we recommend that you define separate document types and warehouse process types for TCD in Customizing. EWM can use TCD-relevant document types to find TCD-specific warehouse process types. For more information, 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. For more information about the warehouse process type, see the IMG for EWM under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type. ●

You have defined the mapping of the document types from the ERP system in EWM, in Customizing. For more information, see the IMG for EWM under Interfaces → ERP Integration → Delivery Processing → Map Document Types from ERP System to EWM.

We deliver Business Configuration Set (BC Set) /SCWM/DLV_TCD, which makes settings for Customizing in the delivery. You have to deactivate SAP GTS for TCD-relevant document types manually. For more information, see the documentation of the BC set.

Process The following graphic provides an overview of the process flow in EWM for stock transfer orders in the ERP system. For sales orders from SAP CRM, the process flow in EWM is more or less identical. However, the goods are sent to the customer after posting goods issue from the last CD warehouse. The ERP system generates the outbound delivery out of the delivering warehouse from the SAP CRM sales order.

SAP Extended Warehouse Management (SAP EWM)

510

548

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

549

SAP Online Help

20.07.2007

...

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

SAP Extended Warehouse Management (SAP EWM)

510

550

SAP Online Help

20.07.2007

You use an ad-hoc warehouse task if required to move the HU to another storage bin. For example, 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, otherwise the TCD process would be finished. EWM always use the highest-level HU to generate the HU WT. If you are working with nested HUs, it can happen that the CD-relevant HU is located within the nested HU. When you pick a TCD-relevant HU, EWM uses a stock removal HU WT to update both the corresponding inbound delivery and the corresponding outbound delivery order simultaneously in EWM. In the inbound delivery, EWM updates the plan data and actual data for the status and quantity. In the outbound delivery order, EWM also updates the plan data and actual data for the status and quantity. For more information about updating quantities in HUs, see HU Integration in Delivery Processing [Seite 136]. For more information about updating quantities and status in putaway and stock removal, see Creation of Warehouse Tasks for Putaway [Seite 302] or Creation of Warehouse Tasks for Stock Removal [Seite 319] under Activities. b. When EWM2 generates the pick-HU WT, the system determines the destination storage bin, such as the staging area in goods issue. c. You confirm the pick-HU WT for the outbound delivery order. d. You move the HU to the specified destination storage bin, for example the goods issue area. e. You load a truck with the HU. 11. EWM2 updates the inbound delivery and the outbound delivery order with the picking data. You post goods issue in CD warehouse EWM2. EWM2 sends the updated EWM2 outbound delivery to the ERP system. If the routing guide does not have any further TCD-relevant steps planned, then the ERP system generates the inbound delivery for receiving warehouse EWM3. Otherwise the ERP system generates another inbound and outbound delivery for the next CD warehouse. Steps 7 to 10 are then repeated. 12. In EWM3 you post goods receipt and execute your warehouse activities. 13. EWM3 informs SAP APO about the updated inbound delivery. 14. SAP APO updates the stock information.

Result ●

You have performed a TCD process and moved the delivered HU directly from the goods receipt area to the goods issue area, for example. The CD route went from delivering warehouse EWM1 to receiving warehouse EWM3 via CD warehouse EWM2.

●

EWM1, EWM2 and EWM3 have all sent the updated data of the inbound and outbound delivery to the ERP system.

●

The ERP system has generated an inbound and outbound delivery for the CD warehouse.

●

You have posted goods receipt and goods issue in the respective warehouse.

●

EWM has updated the status and quantities for putaway for the inbound delivery and for picking for stock removal.

SAP Extended Warehouse Management (SAP EWM)

510

551

SAP Online Help ●

20.07.2007

SAP APO has updated its stock information.

SAP Extended Warehouse Management (SAP EWM)

510

552

SAP Online Help

20.07.2007

Example Scenario for TCD with Storage Control Purpose In contrast to the basic Transportation Cross Docking [Seite 547] scenario (TCD scenario), you are working with a nested handling unit (HU) and Process-Oriented Storage Control [Seite 336] in this more complex TCD scenario. You receive an inbound delivery with a nested putaway HU that contains two further products. 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 determines a goods receipt (GR) storage process for the highest-level putaway HU. The highest-level putaway HU correspondingly runs through all steps of the GR process, including Deconsolidation [Seite 298]. During deconsolidation, 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. You move the TCD HU to the GI zone after deconsolidation. If EWM determines a storage process for process-oriented storage control in goods issue (GI) for this TCD HU after deconsolidation, EWM processes the individual steps according to the warehouse process. You perform the further steps of putaway for the putaway HU.

Prerequisites ●

You have carried out the Customizing for Transportation Cross Dockingapurl_link_0004_0004_0006.

●

You defined warehouse processes. For more information, see the implementation guide (IMG) for EWM under Cross-Process Settings → Warehouse Task → Define Process-Oriented Storage Control.

●

If EWM is to create the pick HU warehouse task (pick HU WT) automatically, the current process step must be indicated with the Prod/HU WT indicator. 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. Select a definition and choose Assign Storage Process Step in the navigation tree. Select the Prod/HU WT indicator.

●

If EWM is to create follow-up WTs, you have set the Auto. WT indicator for automatic follow-up WT creation. To do so, in Customizing for EWM under Cross-Process Settings choose Warehouse Task → Define Process-Oriented Storage Control and in the navigation tree, Storage Process Definition. Select a definition and choose Assign Storage Process Step in the navigation tree. Select the Auto. WT indicator.

Process ... ...

1. Since you are working with nested handling units (HUs) and process-oriented storage control in TCD, EWM determines the putaway steps for the highest-level HU first (for example, unloading and deconsolidating). 2. EWM creates HU warehouse tasks (HU WTs) that move the highest-level HU, and performs the necessary putaway steps for it. 3. After the GR posting, either you or EWM can create a pick WT for the TCD HU. Since only packed products are relevant in TCD, EWM does not create a pick HU WT. This means that you always pick the whole HU in TCD. If the corresponding outbound delivery was assigned to a wave beforehand, you can create the pick HU WT by releasing the wave [Seite 771]. However, you can also create the pick HU WT manually. If you have set the Prod/HU WT indicator in the Customizing settings for the current process step, EWM creates the pick HU WT automatically.

SAP Extended Warehouse Management (SAP EWM)

510

553

SAP Online Help

20.07.2007

If the putaway steps of the highest-level HU have not yet been completed, EWM creates inactive pick HU WTs. If the putaway steps of the highest-level HU have been completed (for example, after you have deconsolidated the highest-level HU), EWM activates the pick HU WTs. For a detailed process flow description, see Detailed Process Description [Seite 555].

SAP Extended Warehouse Management (SAP EWM)

510

554

SAP Online Help

20.07.2007

Detailed Process Description Purpose The following provides an example detailed description for a transportation cross-docking scenario (TCD scenario) with storage control.

Prerequisites ●

You have carried out the Customizing for Transportation Cross-Docking [Seite 547].

●

You defined warehouse processes. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Warehouse Task → Define Process-Oriented Storage Control.

●

If EWM is to create the pick handling unit warehouse task (pick HU WT) automatically, the current process step must be indicated with the Prod/HU WT indicator. 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. Select a definition and choose Assign Storage Process Step in the navigation tree. Select the Prod/HU WT indicator.

●

If EWM is to create follow-up WTs, you have set the Auto. WT indicator for automatic follow-up WT creation. 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. Select a definition and choose Assign Storage Process Step in the navigation tree. Select the Auto. WT indicator.

Process The following figure provides an overview of the example scenario for TCD with storage control.

SAP Extended Warehouse Management (SAP EWM)

510

555

SAP Online Help

20.07.2007

Goods Receipt Unload HU WT GR

1

GR

Inbound Delivery WT creation Outbound Delivery WT creation

Deconsolidation 8010

Complete HU

GR

GR

Inbound Delivery WT confirmation

GR GR

Final Stor. Type

GI Outbound Delivery WT confirmation

GI

HU User GI WT VAS GI GR

GI

GI

GI

GI

Staging Area

GI Packing Stn.

GI VAS Station

User GI

handling unit a user-defined process step warehouse task value-added service procee steps relevant for goods issue process steps relevant for goods receipt

1

Creation of a pick or putaway WT HU WT inactive pick HU WT active pick HU WT inactive product putaway WT active product putaway WT

...

1. You are working in a warehouse with the following layout. ○

Goods receipt doors (GR doors)

○

GR zone

○

Deconsolidation stations

○

Stations for value-added services

○

Packing stations

○

Goods issue zone (GI zone)

○

GI doors

A truck brings an inbound delivery to the GR door.

SAP Extended Warehouse Management (SAP EWM)

510

556

SAP Online Help

20.07.2007

The inbound delivery contains nested HU1 within which TCD HU11 and putaway HU12 are located. EWM has already created an outbound delivery order for TCD HU11. In storage control, HU1 contains a storage process for GR. 2. You post the GR for the inbound delivery. 3. The unload WT for HU1 is either created by you or by EWM. The inactive pick HU WT for TCD HU11 is either created by you or by EWM. You set the Prod/HU WT indicator (see 'Prerequisites') so that EWM can create the inactive pick HU WT. EWM creates the inactive putaway WT for putaway HU12.

However, you can also create the pick HU WT manually via the user interface. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task for Warehouse Request → Stock Removal for Outbound Delivery Order. When EWM creates the pick HU WT, it simultaneously updates the status and quantities in the inbound and outbound deliveries in EWM (see Updating the Inbound Delivery in the GR Process [Seite 271] and Updating the Outbound Delivery Order in the GI Process [Seite 339]). If you attempt to put away an HU in a final storage type for which TCD is necessary, EWM displays a corresponding error message. Since TCD is involved, there are no products for putaway. 4. Since the consolidation groups for TCD HU11 and putaway HU12 are different, EWM determines that deconsolidation is necessary in accordance with the Customizing settings. 5. You move the highest-level HU1 to deconsolidation station 8010 and confirm the pick HU WT for TCD HU1. 6. You deconsolidate HU1 there. You perform the following for TCD HU11: a. You pack TCD HU11 from HU1 into TCD HU13. b. You complete TCD HU13. During this, EWM activates the pick HU WT and creates a corresponding warehouse order. If EWM determines a stock removal process via the warehouse order, EWM transfers it to the TCD HU13. c. The pick HU WT is either confirmed by you or by the system. d. EWM updates the inbound delivery and the outbound delivery order. If the Auto. WT indicator is set for the current process step (see ‘Prerequisites’), EWM creates a stock removal HU WT according to the next process step for TCD HU13 (a user-defined goods issue step, for example). If the Auto. WT indicator is not set for the current process step, EWM does not create a stock removal HU WT for TCD HU13 and TCD HU13 remains at the deconsolidation station. e. You confirm the stock removal WT. You perform the following for putaway HU12: ...

a. You pack the products of putaway HU12 into putaway HU14. b. You complete TCD HU14.

SAP Extended Warehouse Management (SAP EWM)

510

557

SAP Online Help

20.07.2007

During this, EWM activates the putaway WT. c. You put away the products of putaway HU14. 7. If the storage process for stock removal contains a loading step, you can load TCD HU13 using a load WT.

Results You have deconsolidated a nested HU that was delivered, you have performed TCD with repacking for the TCD HU, and you have put away the putaway HU. EWM has correspondingly updated the statuses and quantities of the inbound and outbound deliveries for the TCD HU.

SAP Extended Warehouse Management (SAP EWM)

510

558

SAP Online Help

20.07.2007

Push Deployment (PD) and Pick from Goods Receipt (PFGR) Purpose Push deployment [Extern] (PD) and pick from goods receipt [Extern] (PFGR) are unplanned cross-docking processes. For an unplanned cross-docking process, you work with standard inbound deliveries and start by using the standard goods receipt process. When you post goods receipt, Extended Warehouse Management (EWM) checks whether the warehouse process type and stock type are relevant for putaway delay [Extern]. If they are relevant, EWM starts the putaway delay. By doing this, EWM delays the generation of the warehouse tasks for putaway. If the warehouse process type and stock type are not relevant, EWM generates the warehouse tasks for putaway without delay. This means that it does not perform PD or PFGR. SAP Advanced Planning & Optimization (SAP APO) defines whether an inbound delivery is PD-relevant or PFGR-relevant. This means that SAP APO defines the cross-docking relevance after posting goods receipt.

Push Deployment (PD) You use PD so that you can react to requirement changes and requirement bottlenecks in your warehouse quickly and flexibly. You can use PD to execute stock transfers for inbound deliveries from one warehouse to another at short notice, without having to put away the goods. For more information about push deployment in service parts planning, see Deployment [Extern]. For more information about push deployment in the ERP system, see the SAP Help Portal for SAP ERP under SAP ERP Central Component → Logistics → Logistics - General (LO) → Service Parts Management (LO-SPM) → Transportation CrossDocking → Push Deployment.

Pick From Goods Receipt (PFGR) In PFGR, you can confirm a sales order that is not yet confirmed via the ATP check [Extern] by posting goods receipt for an inbound delivery. You can perform this picking from directly within the goods receipt area; unlike the standard pick procedure, you do not have to put away the products.

Prerequisites ●

You have a system landscape in which you are using EWM, SAP APO and SAP Customer Relationship Management (SAP CRM).

●

You have performed Customizing for push deployment (PD) or pick from goods receipt (PFGR). For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Cross-Docking (CD) → Basic Settings for PD and Pick From GR.

●

You have defined a putaway delay [Extern] for PD or PFGR. For more information, see the IMG for EWM under Cross-Process Settings → Warehouse Task → Define Putaway Delay.

●

If you want EWM to generate pick-warehouse tasks automatically, you have performed the corresponding Customizing in EWM, namely Post-Processing Framework action /SCWM/PRD_OUT_TO_CREATE Create Warehouse Task for Stock Removal. For more information, see the IMG for EWM under Cross-Process Settings → Delivery Processing → Actions.

SAP Extended Warehouse Management (SAP EWM)

510

559

SAP Online Help

20.07.2007

Process The following graphic provides an overview of the process flow in EWM for PD and PFGR. The process for PD and PFGR is largely identical in EWM. The only differences between the processes occur between the start of event-driven quantity assignment and the time when the ERP system generates the related outbound deliveries. The stock allocation of an inbound delivery follows the following principle: ...

1. SAP APO starts by checking whether PFGR is required for the entire stock. EWM generates one or more related outbound delivery orders, if required. 2. SAP APO checks whether PD is required for the remaining stock. EWM generates one or more related outbound delivery orders, if required. 3. The standard putaway process [Seite 300] runs for the remaining stock, and EWM generates one or more related outbound delivery orders. If SAP APO decides that neither PFGR nor PD is required, the remaining stock and stock to be put away can correspond to the inbound stock.

SAP Extended Warehouse Management (SAP EWM)

510

560

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

561

SAP Online Help

20.07.2007

... ...

1. You receive an inbound delivery and post goods receipt (GR) in EWM.

If you are posting goods receipt, you must have authorization to schedule jobs. EWM uses this user authorization to schedule the job for putaway delay.

Goods Receipt Posting You can post goods receipt before unloading a transportation unit or vehicle. If you are working with unloading warehouse tasks, EWM posts the goods receipt at the latest when confirming these unloading warehouse tasks. EWM does not generate a putaway warehouse task until the putaway delay has passed.

We recommend that you post goods receipt before unloading. This allows EWM to call push deployment with the added up quantities from the vehicle. This enables you to make an informed decision regarding replenishment.

Putaway Delay When you post GR, the putaway process begins in EWM for the decision in SAP APO as to whether EWM is to execute PD or PFGR. ○

If SAP APO sends this decision to the ERP system within the putaway delay, the ERP system reserves the required stock and informs EWM about this decision. If EWM is to perform PD or PFGR, it must generate the pickwarehouse tasks during the putaway delay due to the decision made in SAP APO.

○

If SAP APO sends this decision to the ERP system after the putaway delay, EWM receives it too late. EWM attempts to generate pick-warehouse tasks, but the system is unable to find any free stock. The free stock has already been assigned to putaway warehouse tasks.

2. EWM updates the inbound delivery and its stock for received on dock (ROD stock). EWM sends the updated inbound delivery to the ERP system. 3. The ERP system updates its related inbound delivery. It increases its ROD stock within inventory management. 4. Inventory management in the ERP system uses the APO Core Interface (CIF) to send the absolute and the new stock to SAP APO. Inventory management calls SAP APO for each goods movement, and informs SAP APO about the stock change. 5. SAP APO maps the ERP stock type to an ATP stock type.

We predefine the assignment between the ERP stock type and the ATP stock type. You cannot perform Customizing for this assignment. 6. SAP APO starts event-driven quantity assignment (EDQA) [Extern]. 7. SAP APO checks whether a backorder exists, meaning whether PFGR is required. The following describes the process of this check in detail. ○

If a backorder exists, SAP APO calls SAP Customer Relationship Management (SAP CRM). SAP CRM checks whether an unconfirmed sales order still exists. ■

If an unconfirmed sales order does exist, SAP CRM generates a confirmed sales order from it, and informs the ERP system about this.

SAP Extended Warehouse Management (SAP EWM)

510

562

SAP Online Help

20.07.2007 The ERP system generates an outbound delivery and checks whether stock belonging to stock category received on dock (ROD stock) exists for this outbound delivery. This means that the ERP system looks for stock in the goods receipt area. The ERP system informs EWM about the outbound delivery. If SAP CRM does not require the entire stock of the inbound delivery for PFGR, SAP APO checks whether PD is required for the remaining stock. If PFGR is required, SAP APO generates a stock transfer order and informs the ERP system about this.

■

If no unconfirmed sales order exists, SAP APO checks whether PD is required. If PD is required, SAP APO generates a stock transfer order and informs the ERP system about this.

EWM generates one or more related outbound delivery orders, outbound deliveries for outbound delivery orders, and pick-warehouse tasks for outbound deliveries, depending on the decisions made in SAP APO. 8. You execute picking. If no backorder exists, or if neither PFGR nor PD is required, SAP APO does not report anything to the ERP system. After the putaway delay has passed, EWM performs the standard putaway process for the remaining stock, meaning it generates putaway warehouse tasks.

Result SAP APO has checked whether PFGR or PD is required, and triggered the necessary steps in SAP CRM and EWM where required. EWM has generated related outbound delivery orders and pick-warehouse tasks, corresponding to the decision in SAP APO. If EWM has determined that the system has not assigned the entire stock for PFGR or PD, then EWM has generated standard putaway warehouse tasks for the inbound delivery. You execute the required putaway activities [Seite 300] for these putaway warehouse tasks and confirm the putaway warehouse tasks.

SAP Extended Warehouse Management (SAP EWM)

510

563

SAP Online Help

20.07.2007

Example Scenario for PD/PFGR with Storage Control Purpose You are working in a push deployment process (PD process) with process-oriented storage control [Seite 336] and are performing picking for goods receipt (PFGR) for a mixed handling unit (HU). You receive an inbound delivery with a nested HU (putaway HU) that contains three products. PD or PFGR is necessary for one of these products. The other two products are for putaway. Accordingly, you perform deconsolidation for the putaway HU. You unpack the putaway HU and you repack the product that requires PD or PFGR into another HU. You move this HU to another goods issue zone (GI zone). If Extended Warehouse Management (EWM) determines a storage process for process-oriented storage control in GI for this HU after deconsolidation, EWM processes the individual steps according to the warehouse process. You pack the other two products into a putaway HU. You perform the further steps of putaway for this putaway HU.

Prerequisites ●

You have carried out the Customizing for PD and PFGR [Seite 559].

●

You defined warehouse processes. For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Warehouse Task → Define Process-Oriented Storage Control.

●

If EWM is to create follow-up WTs, you have set the Auto. WT indicator for automatic follow-up WT creation. 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. Select a definition and choose Assign Storage Process Step in the navigation tree. Select the Auto. WT indicator.

Process The following figure provides an overview of the example scenario for a PD/PFGR process with storage control.

SAP Extended Warehouse Management (SAP EWM)

510

564

SAP Online Help

20.07.2007

1 Goods Receipt Unload HU WT GR

GR

Inbound Delivery WT creation Outbound Delivery WT creation

Deconsolidation 9005

Complete HU

GR

Inbound Delivery WT creation

GR GR

Final Stor.Type

GI Outbound Delivery WT confirmation

GI

HU User GI WT VAS GI GR

GI

GI

GI

GI

Staging Area

GI Packing Stn.

WA VAS Station

User GI

handling unit a user-defined process step warehouse task value-added service process steps relevant for goods issue process steps relevant for goods receipt

1

Putaway Wt creation HU WT inactive pick product WT active product HU WT inactive putaway product WT active putaway product WT

...

1. You are working in a warehouse with the following layout. ○

Goods receipt doors (GR doors)

○

GR zone

○

Deconsolidation stations

○

Stations for value-added services

○

Packing stations

○

GI zone

○

GI doors

A truck brings an inbound delivery to a GR door. The inbound delivery contains nested HU1 (putaway HU) that contains products P1, P2 and P3.

SAP Extended Warehouse Management (SAP EWM)

510

565

SAP Online Help

20.07.2007

For HU1, EWM determines a storage process for the GR that then marks a process step for unloading. 2. You post the GR for the inbound delivery. For P1, EWM determines that the warehouse process type and the stock type are relevant for the putaway delay [Extern]. By doing so, EWM delays the creation of the unload WT and the putaway product WTs. 3. SAP Advanced Planning & Optimization (SAP APO) determines that a PD or a PFGR is necessary for P1 and informs the ERP system of this. The ERP system creates an outbound delivery for P1 and sends it to EWM (see Push Deployment (PD and Pick From Goods Receipt (PFGR) [Seite 559], step 7). 4. EWM performs the following within the putaway delay: a. EWM creates an inactive pick product WT for P1 that links the GR zone to the GI zone. This WT reserves the stock for P1. b. EWM updates the inbound delivery and the outbound delivery order. 5. EWM performs the following steps after the putaway delay: a. EWM creates corresponding inactive putaway product WTs for P2 and P3. b. EWM updates the corresponding inbound delivery. c. EWM creates an active unload HU WT for HU1. Since the destination storage bins and pick product WTs have different activity areas [Extern], EWM checks whether deconsolidation is necessary. EWM determines that deconsolidation is necessary for HU1 due to the Customizing settings. Accordingly, EWM creates an active HU WT that links the GR zone to the deconsolidation station. EWM simultaneously updates the inactive pick product WT for P1 and the inactive putaway WTs for P2 and P3. These inactive WTs now also link the GR zone to the deconsolidation station. 6. You move HU1 to deconsolidation station 9005 and perform deconsolidation. You perform the following steps for P1: a. You pack P1 into another HU (HU2). b. Again, EWM creates a corresponding inactive pick product WT for P1. c. You complete deconsolidation for HU2. d. EWM activates the pick product WT and creates a corresponding warehouse order. If EWM determines a stock removal process via the warehouse order, EWM transfers it to the WT for HU2. If the next process step of this stock removal process is staging and you have set the Auto. WT indicator (see 'Prerequisites'), EWM creates a follow-up HU WT for HU2. This HU WT links the deconsolidation station to the GI zone. If you have not set the Auto. WT indicator, EWM does not create a follow-up HU WT for HU2. HU2 remains at the deconsolidation station. e. You bring HU2 to the GI zone and confirm the HU WT. f. EWM updates the inbound delivery and the outbound delivery order. You perform the following steps for P2 and P3: ...

a. You repack P2 and P3 into a putaway HU (HU3). b. EWM creates corresponding inactive putaway WTs. c. You complete deconsolidation for HU3. d. EWM activates the corresponding inactive putaway WTs. e. You perform putaway for P2 and P3 of HU3 and confirm the putaway WTs.

SAP Extended Warehouse Management (SAP EWM)

510

566

SAP Online Help

20.07.2007

7. If the storage process for stock removal contains a loading step, you can load HU2 using a load WT.

SAP Extended Warehouse Management (SAP EWM)

510

567

SAP Online Help

20.07.2007

Additional Functions in Cross-Docking Use This section includes information about the following: ●

Business Add-Ins in Cross-Docking

●

Make Settings for Exception Handling in Cross-Docking

●

Example Scenario for Transportation Cross-Docking (TCD) with Storage Control

SAP Extended Warehouse Management (SAP EWM)

510

568

SAP Online Help

20.07.2007

Business Add-Ins in Cross-Docking Use You can use the following Business Add-Ins (BAdIs) in cross-docking to influence the way planned or unplanned cross-docking is processed.

Features The following table gives you an overview of which BAdI you can use for which cross-docking process (CD process). CD Process

BAdI Name

Use

Additional Information

Push Deployment (PD) and Pick from Goods Receipt (PFGR)

BAdI: Putaway Delay Determination

You can use this BAdI to determine the duration of putaway delay during warehouse task creation.

For more information, see the Implementation Guide (IMG) under Extended Warehouse Management → Business Add-Ins (BAdIs) for Extended Warehouse Management → Cross-Process Settings → Warehouse Task → Warehouse Task for the Warehouse Request → BAdI: Putaway Delay Determination

Push Deployment (PD) and Pick from Goods Receipt (PFGR)

BAdI: Creation of Warehouse Task in a Job Through Putaway Delay

If you are working with putaway delay, you can use this BAdI to reassemble packages of the warehouse tasks that are generated in a job.

For more information, see the Implementation Guide (IMG) under Extended Warehouse Management → Business Add-Ins (BAdIs) for Extended Warehouse Management → Cross-Process Settings → Warehouse Task → Warehouse Task for the Warehouse Request → BAdI: Creation of Warehouse Task in a Job Through Putaway Delay

/SCWM/EX_DLV_TOWHR_PTD L_DET

/SCWM/EX_DLV_TOWHR_PTD L_JOB

SAP Extended Warehouse Management (SAP EWM)

510

569

SAP Online Help

20.07.2007

Make Settings for Exception Handling in CD In Extended Warehouse Management (EWM), you use exception codes to describe exception situations in the warehouse. You can define an exception code for different document types, such as for inbound deliveries or outbound deliveries. When EWM executes an exception code, the execution always refers to exactly one business context (inbound or outbound delivery). Since EWM updates both the inbound and the outbound delivery for certain processes in cross-docking (CD) (Updating the Inbound Delivery in the GR Process [Seite 271], Updating the Outbound Delivery Order in the GI Process [Seite 339]), an exception can have an effect on both the inbound and the outbound delivery at the same time. In the Customizing settings, you therefore define whether and how EWM is to adjust the inbound delivery quantities or outbound delivery quantities.

Customizing To use exception handling in CD, you must make the following settings in Customizing: ●

If you want an exception to adjust delivery quantities in CD, you have assigned a process code for the inbound delivery item type and outbound delivery item type when defining the exception code for Delivery Adjustment in Case of Differences. For example, you have assigned process code I002 Adjust to Maximum Quantity to item type IDLV for the inbound delivery, and process code O002 Adjust to Maximum Quantity to item type ODLV for the outbound delivery.

●

If the item type does not correspond to the business context, you have also set the CD indicator for this item type. Doing this ensures that EWM also adjusts the delivery quantity of this item type.

You confirm a pick-warehouse task (pick-WT) for a transportation cross-docking handling unit (TCD-HU). EWM proposes an HU. However, you notice that the proposed HU does not exist. For a case such as this, you have defined exception code DTCD for the business context TPI Whse Task: Confirm (Stock Removal) in the Customizing settings. You want EWM to use this exception code to adjust both the inbound delivery quantity and the outbound delivery quantity. You have therefore defined the following when defining the exception code for the Delivery Adjustment in Case of Differences: ●

You have selected the CD indicator for the item type of the inbound delivery IDLV, since this item type does not belong to business context TPI Whse Task: Confirm (Stock Removal), rather to business context TPT Whse Task: Confirm (Putaway). You have also assigned process code I001, which refers to the inbound delivery, to this item type.

●

You have not set the CD indicator for the item type of the outbound delivery ODLV, since this item type does belong to business context TPI Whse Task: Confirm (Stock Removal). You have also assigned process code I002, which refers to the outbound delivery, to this item type.

For more information, see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Exception Handling → Define Exception Codes.

SAP Extended Warehouse Management (SAP EWM)

510

570

SAP Online Help

20.07.2007

Serial Number Definition Character string that is given to a product in addition to a product number in order to differentiate the individual piece from all the other pieces. The combination of product number and serial number is unique.

Use You use serial numbers if you want to identify or trace single units in the warehouse. Extended Warehouse Management (EWM) only controls the serial numbers (as a movement date) until goods issue posting. You can also extract the serial number as textual information from the delivery document, meaning that further information is saved only by the ERP system. If you use the data record for master data in the ERP system, you can carry out evaluations with the serial number history and check partner data, for example. For more information about data records for master data, see Logistics → Logistics General (LO) → Logistics Basic Data (LO-MD) → Administration of Serial Numbers (LO-MD-SN) → Serial Number Master Record in the SAP Library under SAP Central Component. For more information about serial numbers, see Using the Serial Number Requirement [Seite 576].

Structure In EWM, you can specify a serial number with a maximum length of 30 characters. However, if you want to use data records for master data in the ERP system, the serial number in EWM can only have 18 characters. If necessary, you can use the Business Add-In (BAdI) Converting Serial Numbers ERP – EWM /SCWM/EX_ERP_SN for mapping the serial number between the ERP system and EWM. This also allows you to work with 30 digit serial numbers in EWM. For more information about setting the maximum length of the serial number, see the Implementation Guide (IMG) for EWM under Master Data→ Product → Define Serial Number Profile → Serial Number: Warehouse Number Settings. You can find the partner data in the master record of the serial number in the ERP system. Here you can define, for example, which companies are responsible for the maintenance of the serialized product using arbitrary partner roles and partners with Customizing. For more information about partner data, see Logistics → Logistics General (LO) → Logistics Basic Data (LO-MD) → Serial Number Management (LO-MD-SN) → Serial Number Master Record in the SAP Library under SAP ERP Central Component. If you want EWM to automatically carry out mapping between your specified serial numbers and the serial numbers saved in the database, you can use the BAdI Converting Serial Numbers (/SCWM/EX_SER_DISPLAY). You can use this BAdI to determine your own conversion criteria. A restricting factor here is that the conversion criteria only influence the display, input and output of serial numbers and do not influence the saving of serial numbers. For more information, see the BAdI documentation.

Integration If you want to use serial numbers, you must firstly determine a serial number profile for a product. You assign this serial number profile to the master record of the product. You can then use serial numbers. For more information about the definition of serial number profiles, see the IMG for EWM under Master Data → Product → Define Serial Number Profiles.

SAP Extended Warehouse Management (SAP EWM)

510

571

SAP Online Help

20.07.2007

Example Company X manufactures solar panels. It produces three different types: ●

Type A

●

Type B

●

Type C

A product master record exists in the company X’s system for each type produced. For checking purposes, the company wants to know which customer received which type and which serial number(s) was/were delivered to customers for the shipment of each individual solar panel. To do so, you assign a serial number to every solar panel that is manufactured, which, together with the product number, identifies the product uniquely. Object

Product Number

Serial Number

Solar Panel 1

SP-A

94-05-01

Solar Panel 2

SP-A

94-05-02

Solar Panel 3

SP-B

94-05-01

Solar Panel 4

SP-B

94-05-02

Solar Panel 5

SP-C

94-05-01

SAP Extended Warehouse Management (SAP EWM)

510

572

SAP Online Help

20.07.2007

Serial Number Profile Definition A group of data, condensed under a four character abbreviation, that determines the conditions and business activities for the allocation of serial numbers to single product units. You must enter the serial number profile in the master record of the product, the single units of which must be provided with a serial number.

Use In the system configuration in Customizing of the ERP system, you define a serial number profile that is valid for all warehouse numbers, in other words, is warehouse-numberindependent. You can, however, also define a warehouse-number-dependent serial number profile in Customizing for Extended Warehouse Managemant (EWM). Firstly, EWM searches for the warehouse number-dependent serial number-profile. Only if it does not find one does it use the warehouse number-independent serial number profile. In this way, you can make a product require a serial number [Extern] in one warehouse and not require one in another warehouse. If you want to work with serial number profiles, assign the serial number profile in the ERP system to a product master record. For more information about the definition of serial number profiles, see the Implementation Guide (IMG) for EWM under Master Data → Product → Define Serial Number Profiles. Once you have assigned a serial number profile to a product master record in the ERP system, you can specify serial numbers in EWM independently of the serial number requirement. ●

For serial numbers for document items, you can determine whether serial numbers have to be entered (are mandatory) for an item type. If you have not determined this, the entry of serial numbers is optional.

●

With serial numbers at warehouse number level, you always enter a serial number in the inbound or outbound delivery (mandatory) but you also have the option of entering a serial number during another process step.

●

You can enter serial numbers in inventory management for every change in stock (mandatory).

●

If you do not want to work with serial numbers in a warehouse, then you determine No Serial Number Requirement as the serial number requirement for this warehouse, in Customizing for EWM under Master Data → Product → Define Serial Number Profile.

For more information about entering serial numbers, see Entering and Editing Serial Numbers [Seite 587].

Structure The serial number profile contains the following information: ●

Warehouse number, if you are working with a warehouse number-dependent serial number profile

●

Four character abbreviation for the serial number profile

●

Serial number profile description

●

Prefix, if you use a prefix at the beginning of the serial number (optional)

SAP Extended Warehouse Management (SAP EWM)

510

573

SAP Online Help

20.07.2007

You are using the number range interval 01 with the ‘from’ number 1000 and the ‘to’ number 2000 and specify ENGINE as the prefix in Customizing. EWM creates the following serial numbers, for example: ENGINE1000 or ENGINE1001. ●

Serial number If EWM is to use a number range object and a number range number to determine the serial number, the serial number profile contains the following information: ■

Number range object [Extern]

■

Number range number that determines the number range interval [Extern]

You want EWM to use an automatic serial number allocation from the same number range interval ( 01) for two different products (A and B). In Customizing for the ERP system, you assign the same serial number profile (SNP1) to the master record of products A and B. In Customizing in the serial number profile SNP1, you specify the number range object Z1 and the number range interval 01. EWM automatically allocates serial numbers from the number range interval 01 to all products that you have assigned to the serial number profile SNP1 , for example A and B. ●

Indicator for automatic numbering, if EWM is to continue counting from the last allocated serial number.

●

Serial number requirement type [Seite 576], for which you have to execute a serialization, for example, serial number requirement for document items

SAP Extended Warehouse Management (SAP EWM)

510

574

SAP Online Help

20.07.2007

Provisional Serial Number Definition Character string that the system automatically assigns to products requiring serial numbers (serial numbers at warehouse number level or in inventory management). The provisional serial number must be replaced before the execution of certain process steps in the goods receipt process, by entering a valid serial number manually.

Use Extended Warehouse Management (EWM) always requires the serial numbers at warehouse number level [Seite 583] or in inventory management [Seite 585] before the goods receipt posting. If you set the Prov SNs indicator in Customizing, EWM automatically assigns a provisional serial number, if you have not already entered a valid serial number. You replace this serial number with your own in a subsequent goods receipt process.

If you want to track information about serial numbers in ERP, do not use provisional serial numbers. As soon as you use provisional serial numbers and replace them with your own serial numbers at a later point in time, EWM no longer reports these serial numbers to ERP, meaning that ERP does not have an up-to-date information regarding the status of the serial numbers in EWM. For more information about the prerequisites for using serial numbers and provisional serial numbers, see Using the Serial Number Requirement [Seite 576].

Structure A provisional serial number always begins with $ and has 30 characters.

Integration EWM only uses provisional serial numbers for serial numbers at warehouse number level or in inventory management.

Example You unload a commercial truck and post the goods receipt. At this point, you do not want to specify any serial numbers. In Customizing, under Extended Warehouse Management → Master Data → Product → Define Serial Number Profiles → Serial Numbers: Settings for Warehouse Number, you have set the Prov.SNs indicator. EWM automatically assigns provisional serial numbers. You do not specify serial numbers until deconsolidation [Seite 298].

SAP Extended Warehouse Management (SAP EWM)

510

575

SAP Online Help

20.07.2007

Using the Serial Number Requirement Purpose You use serial numbers to identify a product uniquely and to provide yourself with an overview of which products you have sold to which customers. The serial number is only unique in conjunction with a product, for example, cell phone CELL PHONE 0000000012345 or ENGINE0000000012345. For example, you can use serial numbers in the following instances: ●

If a freight forwarder damages a pallet during transportation, Extended Warehouse Management (EWM) can show you which engines were on the palette and could now potentially be damaged.

●

You can tell if a partner reports a product as having been stolen, but later sends it to you for maintenance.

●

If a customer returns a damaged engine, you can determine whether it is actually the engine that you supplied them with.

●

If, during quality control, you determine that a production error has occurred, you can identify the affected product groups by using serial numbers. If necessary, you can also identify the customers to which you have already sold damaged products and inform them of this.

You can use the following serial number requirments: ●

Serial Numbers for Document Items [Seite 581]

●

Serial Numbers at Warehouse Number Level [Seite 583]

●

Serial Numbers in Inventory Management [Seite 585]

Prerequisites For a description of the prerequisites, see Making Settings for Serial Numbers (ERP-System and EWM) [Seite 579].

Process The following graphic provides an overview of the process flow for the individual serial number requirements. ... ...

SAP Extended Warehouse Management (SAP EWM)

510

576

SAP Online Help

20.07.2007

Carry out change in stock

System determines serial number profile

User is in delivery processing

Serial Numbers for Document Items Entry of required serial numberr •

Goods receipt Serial number with advanced shipping notification by scanning or entering manually

•

User is in delivery processing

Serial Numbers at Warehouse Number Level

Serial Numbers in Inventory Management

Entry of the required serial number

Entry of the required serial number for every goods movement by scanning or entering manually

• Goods receipt and issue serial number by scanning or entering manually

Goods Issue Serial number by scanning or entering manaully

System saves serial number

Reduced Administrative Expenditure

Detailed Information

1. If you execute a change in stock, EWM identifies the serial number profile [Seite 573] that belongs to a product. Depending on your settings in Customizing, this serial number profile can be warehouse number dependent or independent.

SAP Extended Warehouse Management (SAP EWM)

510

577

SAP Online Help

20.07.2007

The customizing scout [Extern] in the ERP-System sends the product data and the information on which serial number profile belongs to which product to EWM using the APO Core Interface (CIF) [Extern]. For more information about the Customizing Scout, see the Help Portal help.sap.com under Documentation → SAP NetWeaver → Prior SAP NetWeaver 04 → SAP Solution Manager → Customizing-Synchronization → Customizing Scout [Extern]. 2. EWM copies either the serial number from the ERP system or you enter it manually. If you choose the serial number requirement, you have to weigh up administrative expenditure against the degree of detail of the information. Serial number requirement

Entry of Serial Number in Goods Receipt

Entry of Serial Number in Goods Issue

Entry of Serial Number in Internal Warehouse Movements

Information

Serial Numbers for Document Items

Serial number with advanced shipping notification by scanning or entering manually; mandatory if the item type of the delivery has been determined in Customizing

Serial number with advanced shipping notification; mandatory for confirmed quantities if the item type of the delivery has been defined in Customizing

No entry possible

Check if serial number possible, for example, in the returns process

Serial Numbers at Warehouse Number Level

Serial number with advanced shipping notification by scanning or entering manually

Serial number entered manually or by scanning for confirmed quantities

No entry possible

Information about which serial numbers are available in which warehouse

Serial Numbers in Inventory Management

Serial number with advanced shipping notification by scanning or entering manually

Serial number by scanning or entering manually

If Handling Unit is only partly confirmed, serial numbers by scanning or entering manually

Exact storage bin or stock information

For a detailed process flow description of the individual processes, see Serial Numbers for Document Items [Seite 581], Serial Numbers at Warehouse Number Level [Seite 583], Serial Numbers in Inventory Management [Seite 585]. 3. EWM saves the serial number.

SAP Extended Warehouse Management (SAP EWM)

510

578

SAP Online Help

20.07.2007

Making Settings for Serial Numbers (ERP System and EWM) To use serial numbers in Extended Warehouse Management (EWM), you must make the following Customizing settings:

Settings for the Serial Number Profile in the ERP System In the ERP system, you can specify serial numbers with which you then work in EWM. To do so, you have executed the following in Customizing for the ERP system: ●

You have determined the serial number profile for the ERP system (ERP serial number profile). For more information, see Logistics Execution → Shipping → Basic Shipping Functions → Serial Numbers in the Implementation Guide (IMG) of the ERP.

Do not set up an ERP serial number profile with stock check in Customizing. Goods movement postings originating from EWM do not register serial numbers at the central ERP system. Therefore it is not possible to update serial number data in the ERP system. EWM does not register serial numbers in internal goods movement postings at the ERP system. Therefore, serial numbers in the ERP system do not receive qualified stock information. ●

You have assigned the ERP serial number profile to a material. For more information, see Logistics → Logistics General (LO) → Logistics Master Data (LO-MD) → Administration of Serial Numbers (LO-MD-SN) → Serial Number Profile → Enter Serial Number Profile in Material Master Record.

●

In Customizing for the EWM-specific parameters, you have selected EWM as the external warehouse management system. This results in the SN of WMS indicator being set automatically. In this case, you must make sure that the serial numbers are unique outside the system. In the ERP system and in EWM, there is no cross-system check of the serial numbers created. For more information, see the IMG of the ERP system, under Logistics Execution → Service Parts Management (SPM) → Integrate SPM with Other Components → Edit EWM-specific Parameters.

Settings for Using Serial Numbers in EWM You have executed the following in Customizing for the ERP system so that you can use serial numbers in EWM: You have determined warehouse number-independent serial number profiles for EWM (EWM serial number profiles) that are valid for all warehouses. You have also defined the assignment of these serial number profiles to the products. In doing so, you define which serial number requirement (serial numbers for document items, at warehouse number level, or in inventory management) EWM uses for which product. For more information, see the IMG of the ERP system under Integration with Other SAP Components → Extended Warehouse Management → Additional Material Attributes → Attribute Values for Additional Material Master Fields → Define Serial Number Profile.

Settings for the Serial Number Profile in EWM You have executed the following in Customizing for EWM:

SAP Extended Warehouse Management (SAP EWM)

510

579

SAP Online Help ●

20.07.2007

If you want to overwrite a serial number profile that is not warehouse numberdependent with one that is warehouse number-dependent, you have defined a warehouse number-dependent serial number profile. For more information, see the IMG for EWM under Master Data → Product → Define Serial Number Profiles → Define Warehouse Number-Dependent Serial Number Profiles.

●

For serial numbers for document items, in Customizing for EWM you have determined the item types for which serial numbers are required, that is, you have set the SN indicator (relevant for document-related serialization) for these item types. For more information, see the IMG for EWM:

●

○

Goods Receipt Process → Inbound Delivery → Manual Settings → Define Item Types for the Inbound Delivery Process

○

Goods Issue Process → Outbound Delivery → Manual Settings → Define Item Types for Outbound Delivery Process

○

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

○

Internal Processes in the Warehouse → Delivery Processing → Posting Changes → Manual Settings → Define Item Types for the Stock Transfer Process

If you are already executing a goods receipt posting, but you only want to specify the corresponding serial numbers at warehouse number level or in inventory management when you execute a further goods receipt process, you have set the Prov. SN. indicator in Customizing for EWM, under Master Data → Product → Define Serial Number Profiles → Serial Numbers: Settings for Warehouse Number

SAP Extended Warehouse Management (SAP EWM)

510

580

SAP Online Help

20.07.2007

Serial Numbers for Document Items Purpose You use this serial number requirement to document serial numbers in certain business processes only. For example, you document the serial numbers in an outbound delivery and in a customer return. In doing so you can check whether the piece that the customer has lodged a complaint about is actually the same piece that you delivered to them.

Prerequisites For a description of the prerequisites, see Making Settings for Serial Numbers (ERP-System and EWM) [Seite 579].

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

User is in delivery processing

System determines serial number profile

Entry of required serial number •

Goods receipt Serial number with advanced shipping notification, entered manually or scanned

•

Goods Issue Serial entered manually or scanned

System saves serial number

...

1. You are editing a delivery document, for example, an inbound or outbound delivery. The product in the delivery document requires a serial number. 2. EWM determines the serial number profile that belongs to a product and checks whether you have determined Serial Number Requirement for Document Items as the serial number requirement in Customizing.

SAP Extended Warehouse Management (SAP EWM)

510

581

SAP Online Help

20.07.2007

Next, EWM searches for a product with a warehouse number-dependent serial number profile. If it does not find one, it uses the warehouse numberindependent serial number profile from the ERP system. 3. You receive the serial numbers specified for the product, or you enter them manually. In the goods receipt process, you receive a serial number with the advanced delivery notification, by scanning or entering it manually in the inbound delivery, in warehouse task posting, or in the work center. In the goods issue process, you specify a serial number by scanning or entering it manually in the outbound delivery, in warehouse task posting, or in the Work Center. In Customizing, you define whether entering a serial number is mandatory or optional for individual item types. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Receipt Process → Inbound Delivery → Manual Settings → Define Item Types for the Goods Issue Process → Goods Issue Process → Outbound Delivery → Manual Settings ### Define Item Types for the Outbound Delivery Process. 4. EWM saves the serial number in the delivery and sends it to the ERP system. See Also: Using Serial Numbers in the Delivery [Seite 590]

SAP Extended Warehouse Management (SAP EWM)

510

582

SAP Online Help

20.07.2007

Serial Numbers at Warehouse Number Level Purpose You use this serial number requirement to store serial numbers in goods receipt and goods issue. This provides you with an overview of which serial numbers are available in your warehouse.

Prerequisites For a description of the prerequisites, see Making Settings for Serial Numbers (ERP-System and EWM) [Seite 579].

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

User is in delivery processing or physical inventory processing

System determines serial number profile

Entry of required serial number •

Goods issue and goods receipt Serial number either scanned or entered manually

System saves serial number

...

1. You are processing a delivery document for one of the following processes: ○

for inbound or outbound delivery

○

for a stock transfer

○

for a physical inventory

The product requires a serial number. 2. Extended Warehouse Management (EWM) determines the serial number profile [Seite 573] of the product and checks whether you have determined Serial Number Requirement at Warehouse Number Level as a serial number requirement in Customizing.

SAP Extended Warehouse Management (SAP EWM)

510

583

SAP Online Help

20.07.2007

3. You are in delivery processing and confirm the corresponding warehouse task or you are working with serial numbers at the Work Center. You thereby replace the provisional serial number with the required serial number, either manually or by scanning. You can only execute a goods receipt or goods issue posting if you have specified the required serial number. If you are working with provisional serial numbers [Seite 575] in the goods receipt process, you must replace them with valid serial numbers. You can only do this before confirming the corresponding warehouse task for the final storage bin. For more information about entering serial numbers, see Entering and Editing Serial Numbers [Seite 587]. For internal movements in the warehouse, the serialization requirement for document items does not apply. Therefore, you do not have to specify serial numbers for internal movements in the warehouse. 4. EWM saves the serial number in the delivery and sends it to the ERP system. For more information, see the SAP library under SAP ERP → Logistics → Logistics General (LO) → Logistics Basic Data (LO-MD) → Serial Number Management (LO-MD-SN) → Working with Serial Numbers.

SAP Extended Warehouse Management (SAP EWM)

510

584

SAP Online Help

20.07.2007

Serial Numbers in Inventory Management Purpose You use this serial number requirement to store exact storage bin information for a serial number.

Prerequisites For a description of the prerequisites, see Making Settings for Serial Numbers (ERP-System and EWM) [Seite 579].

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

User is in delivery processing

System determines serial number profile

Entry of the required serial number for every goods movement, either manually or by scanning

System saves serial number

...

1. You execute a change in stock, for example, posting a delivery, internal movements in the warehouse or inventory. 2. Extended Warehouse Management (EWM) determines the serial number profile [Seite 573] of the product and checks whether you have determined Serial Number Requirement in Inventory Management as a serial number requirement in Customizing. 3. You confirm the corresponding warehouse task or you are working with serial numbers in either the Work Center or the delivery. You thereby specify the required serial number, either manually or by scanning. If, during goods movements in the warehouse, you only partly confirm a handling unit and you confirm the corresponding warehouse task, you must select the required serial numbers from the serial numbers specified. In the inventory, you specify the required serial number together with your inventory count result.

SAP Extended Warehouse Management (SAP EWM)

510

585

SAP Online Help

20.07.2007

You can only execute a goods receipt posting if you have specified the required serial number. If you are working with provisional serial numbers [Seite 575], you must replace them with valid serial numbers. You can only do this before confirming the corresponding warehouse task for the final storage bin. For more information about entering serial numbers, see Entering and Editing Serial Numbers [Seite 587]. With serial numbers in inventory management, every delivery item is completely serialized, that is, every piece of the delivery item has a serial number. 4. EWM sends the serial number to the Logistic Inventory Management Engine (LIME). 5. LIME saves the serial number. For more information, see the SAP library under SAP ERP → Logistics → Logistics General (LO) → Logistics Basic Data (LO-MD) → Serial Number Management (LO-MD-SN) → Working with Serial Numbers. See Also: Cancellation of Picking [Seite 329]

SAP Extended Warehouse Management (SAP EWM)

510

586

SAP Online Help

20.07.2007

Entering and Editing Serial Numbers Use With serial numbers, you select individual products, which makes them distinguishable. You can work with serial numbers in the following areas: ●

In the delivery

●

At the work center

●

In the EWM monitor

●

In the inventory

●

In the RF environment

●

When confirming a warehouse task

Integration For more information about the integration of the serial number in the delivery, see Integration of the Serial Number in the Delivery [Seite 592].

Prerequisites If you want to serialize a product, you must define a serial number profile [Seite 573].

Features In the following warehouse activities, you can enter a serial number or use Extended Warehouse Management (EWM) to determine one. ●

When confirming a warehouse task

●

When changing a delivery item

●

When packing at the work center

You can specifiy whole serial number ranges instead of individual serial numbers. If you want to work with serial numbers, you can use the following functions: ●

Using serial numbers in the delivery EWM can copy serial numbers from the ERP System in both the goods receipt (GR) process, using an advanced shipping notification, and the goods issue (GI) process, using predetermined serial numbers. If no serial numbers have been predetermined, you must specify the serial number in the delivery in accordance with the serial number profile [Seite 573] in EWM, for example, when you confirm a warehouse task. For more information, see Using Serial Numbers in the Delivery [Seite 590] and Specifying Serial Numbers for Creating a Warehouse Task [Seite 599].

●

Using serial numbers during the stock data transfer You can transfer serial numbers in an inventory data transfer. For more information, see the report documentation for report /SCWM/R_INITIALSTOCKUPLOAD.

●

Using serial numbers in the warehouse management monitor You can display serial numbers in the warehouse management monitor

SAP Extended Warehouse Management (SAP EWM)

510

587

SAP Online Help

20.07.2007

For more information, see Using Serial Numbers in the Warehouse Management Monitor [Seite 604]. ●

Using serial numbers in the warehouse task When EWM creates a warehouse task for serial numbers in Inventory Management, it adopts automatically predetermined serial numbers. When you confirm a warehouse task you can manually specify serial numbers. EWM takes serial numbers into account during the different process steps of a warehouse task, for example, if you only partly confirm a warehouse task, For more information, see Warehouse Task Creation with Reference to a Warehouse Request [Seite 595] and Using Serial Numbers in a Warehouse Task [Seite 597].

●

Using serial numbers in the posting change When you execute a posting change for a product, you can display the list of serial numbers that have undergone a posting change in the detailed overview of the item using the Serial Numbers pushbutton on the Serial Numbers with Posting Changes tab page (and, if necessary, specify the required serial numbers). To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Make Posting Change for Product.

●

Using Serial Numbers in a Radio Frequency Environment (RF Environment) [Seite 605]

●

Using serial numbers in the physical inventory You can specify your serial numbers while counting is taking place and display them in the inventory document. You can also display your serial numbers in the warehouse management monitor and the difference analyzer. For more information, see Using Serial Numbers in the Warehouse Management Monitor [Seite 604].

●

Using serial numbers in the Work Center You can display or edit serial numbers in both the goods receipt process and the goods issue process. For more information about when you can edit serial numbers in the work center, see Using Serial Numbers in the Work Center [Seite 602].

Activities To display serial numbers at warehouse number level, choose Extended Warehouse Management → Monitoring → Warehouse Management Monitor → Stock and Space → Warehouse Serial Number on the SAP Easy Access screen. To display serial numbers in inventory management, on the SAP Easy Access screen, choose Extended Warehouse Management → Monitoring → Warehouse Management Monitor → Stock and Space and one of the following options: ●

Storage Bin → Physical Stock and the Serial Number pushbutton

●

Storage Bin → Available Stock → Physical Inventory and the Serial Number pushbutton

●

Storage Bin → Handling Unit → Physical Stock and the Serial Number pushbutton

●

Physical Stock and the Serial Number pushbutton

●

Available Stock → Physical Inventory and the Serial Number pushbutton

●

Resource → Physical Stock and the Serial Number pushbutton

SAP Extended Warehouse Management (SAP EWM)

510

588

SAP Online Help

20.07.2007

●

Resource → Available Stock → Physical Inventory and the Serial Number pushbutton

●

Handling Unit → Physical Stock and the Serial Number pushbutton

SAP Extended Warehouse Management (SAP EWM)

510

589

SAP Online Help

20.07.2007

Using Serial Numbers in the Delivery Use Extended Warehouse Management (EWM) assigns the serial number to the delivery items in the delivery document. When you are packing a delivery item, EWM also saves the assignment of the corresponding Handling Unit (HU). You can print out the serial numbers together with the delivery note.

Integration For a detailed description on the integration of the serial number in the delivery, see Integration of the Serial Number in the Delivery [Seite 592].

Prerequisites ●

You have made the Customizing settings for the serial numbers. For more information, see Making Settings for Serial Numbers (ERP-System and EWM) [Seite 579].

●

If you want to specify serial numbers in the goods receipt process, then these serial numbers must be specified with the advanced shipping notification in the ERP System. The ERP System assigns these predetermined serial numbers to an ERP inbound delivery and sends the ERP inbound delivery to EWM. EWM copies the predetermined serial numbers into the corresponding inbound delivery notification.

●

If you want to specify serial numbers in the goods issue process, then you must do so in the ERP System in the sales order. The ERP System assigns these predetermined serial numbers to an ERP outbound delivery and sends the ERP outbound delivery to EWM. EWM copies the predetermined serial numbers into the corresponding outbound delivery notification.

Features EWM copies the serial numbers from the ERP System in both the goods receipt and goods issue processes. If no serial numbers have been specified, then you must specify the serial number in the inbound delivery or the outbound delivery order in accordance with the serial number profile in EWM (see Specifying Serial Numbers for Creating a Warehouse Task [Seite 599]. If you have not defined serial numbers for products, EWM copies the serial numbers into the inbound delivery notification or the outbound delivery request. However, EWM deletes these serial numbers from the inbound delivery or the outbound delivery order.

Goods Receipt Process EWM copies the serial number from the ERP system. It permanently saves the serial number that was sent in the inbound delivery notification [Seite 87]. If you have determined the serial number correspondingly, EWM saves it when you make your goods receipt posting in the inbound delivery [Seite 88]. If the inbound delivery does not contain any HU data (that is, the HU does not specify a serial number), you can manually enter or change the serial number in the user interface up until the goods receipt posting takes place. If the inbound delivery contains HU data, carry out the change for the HU data.

Goods Issue Process In the goods issue process, EWM determines the serial number in one of the following ways, or you enter them manually:

SAP Extended Warehouse Management (SAP EWM)

510

590

SAP Online Help

20.07.2007

●

EWM uses the serial number from the warehouse task, for example, the serial number in inventory management.

●

EWM uses the serial number from the HU data.

●

You can enter the serial number manually on the user interface or in the Work Center for the outbound delivery for serial numbers for document items or at warehouse number level.

For more information about the integration of the serial number in the delivery and on communication with the ERP system, see Integration of the Serial Number in the Delivery [Seite 592]. For a description of the processes for the individual serialization requirements, see: ●

Serial Numbers for Document Items [Seite 581]

●

Serial Numbers at Warehouse Number Level [Seite 583]

●

Serial Numbers in Inventory Management [Seite 585]

Printing Serial Numbers EWM automatically prints serial numbers with the delivery note of the corresponding delivery item. For more information, see Printing Delivery Notes [Seite 143].

Activities If you want to change a serial number manually in the goods receipt process, choose the following from the SAP Easy Access screen: Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery and then the Serial Number tab page. If, during the goods issue process, you want to manually enter serial numbers in the user interface of the outbound delivery, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery in the SAP Easy Access screen. If, during the goods issue process, you want to manually enter serial numbers in the work center for serial numbers for document items, choose the following from the SAP Easy Access screen: Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order or Maintain Outbound Delivery and then the Serial Number tab page.

SAP Extended Warehouse Management (SAP EWM)

510

591

SAP Online Help

20.07.2007

Integration of the Serial Number in the Delivery Purpose Serial numbers exist in the delivery for stock transfers and for the goods receipt and goods issue processes. If you have determined the master data of the respective products correspondingly, you can assign serial numbers to each item in the delivery. For serial number assignment, Extended Warehouse Management (EWM) opens a dialogue box in which you can make the desired entries.

If you have determined (in the serial number definition in Customizing) that serial number assignment in the delivery is mandatory, you will only be able to post goods movements if you have created serial numbers for items that require them.

Prerequisites For a description of the prerequisites, see Using Serial Numbers in the Delivery [Seite 590].

Process Goods Receipt Process ...

1. In the goods receipt process, EWM copies the serial numbers from the ERP System into the inbound delivery notification [Seite 87]. 2. Once EWM has copied the data from the ERP System into the inbound delivery notification, EWM also copies the serial numbers from the inbound delivery notification into the inbound delivery [Seite 88]. A prerequisite for this is that you have determined the serialization for the product in the serial number profile. Otherwise EWM does not copy any serial numbers to the inbound delivery. You can make changes to copied serial numbers in the user interface of the inbound delivery up until the goods receipt posting.

Your supplier sends a serial number with the advanced shipping notification. You have determined a serial number profile with serialization for the product. EWM copies the serial number from the inbound delivery of the ERP system to the inbound delivery notification and the inbound delivery. The following graphic provides an overview of the copying of a serial number from the inbound delivery data of the ERP system.

3. Either you or EWM carry out the goods receipt steps. SAP Extended Warehouse Management (SAP EWM)

510

592

SAP Online Help

20.07.2007

Goods Issue Process ...

1. In the goods issue process, EWM copies the serial numbers from the ERP System into the outbound delivery request [Seite 90]. If no serial numbers exist in the ERP System, EWM can receive serial numbers in one of the following ways: ○

○

A warehouse task exists for the outbound delivery order ■

If you confirm a warehouse task for products with the Serial Number Requirement for Document Items or the Serial Number Requirement at Warehouse Number Level, EWM copies the serial numbers from the warehouse task into the outbound delivery order [Seite 91]. You can also manually enter or scan the serial numbers in the outbound delivery order.

■

If you confirm a warehouse task for products with the Serial Number Requirement in Inventory Management, EWM copies the serial numbers from the warehouse task into the outbound delivery order.

No warehouse task exists for the outbound delivery order ■

As soon as you specify a goods movement bin in an outbound delivery order, you can also specify the corresponding serial numbers.

2. Once EWM has copied the data from the ERP System into the outbound delivery request, EWM also copies the serial numbers from the outbound delivery request into the outbound delivery order and the outbound delivery [Seite 93]. A prerequisite for this is that you have determined the serialization for the product in the serial number profile. In other cases, EWM does not copy any serial numbers into the outbound delivery order or the outbound delivery. Unlike with the goods receipt process, you cannot make changes to copied serial numbers in the goods issue process. The following figure provides an overview of the serial number entry options in the outbound delivery.

Goods Issue Process ERP Outbound Delivery

EWM Outbound Delivery Request

EWM Outbound Delivery Order

EWM Outbound Delivery

ENGINE12345

ENGINE12345

ENGINE12345

ENGINE12345

Serial number alw ays copied

Serial number alw ays copied if product is serialized

Serial number alw ays copied if product is serialized

3. Either you or EWM carry out the goods issue steps.

Stock Transfers The process during internal stock transfers (ad-hoc movements, for example) corresponds to that of the goods issue process.

Returns The returns process corresponds to the process for goods receipt that has been described here.

SAP Extended Warehouse Management (SAP EWM)

510

593

SAP Online Help

20.07.2007

Delivery Item Split If the Handling Unit (HU) contains a serial number, you execute an HU-based delivery item split. On the SAP Easy Access screen choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order and from there go to the Create Split Item pushbutton on the HU tab page. If the serial number to be split is not contained in an HU, you carry out the delivery item split in the delivery. On the SAP Easy Access screen choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order and from there go to the Subitem pushbutton on the Items tab page. See Also: ●

Warehouse Task Creation with Reference to a Warehouse Task [Seite 595]

●

Using Serial Numbers in a Warehouse Task [Seite 597]

●

Using Serial Numbers at the Work Center [Seite 602]

●

Using Serial Numbers in an RF Environment [Seite 605]

●

Specifying Serial Numbers for Warehouse Task Creation [Seite 599]

SAP Extended Warehouse Management (SAP EWM)

510

594

SAP Online Help

20.07.2007

Warehouse Task Creation with Reference to a Warehouse Request Use You can display the predetermined serial numbers in the user interface of the inbound delivery, the outbound delivery order or for posting changes. The serial numbers that EWM displays here belong to the open quantity at the time preceding the creation of the warehouse tasks. The displayed serial numbers do not represent the warehouse tasks that have already been created.

Features If you are in the user interface for stock removal or for posting changes, EWM only displays the stock for which serial numbers have been specified on the Stk Can Be Removed tab page or the Other Stock tab page. A prerequisite for this is that EWM has not yet locked the serial numbers for warehouse task creation. When EWM creates the required warehouse tasks for an outbound delivery request or an outbound delivery order, it assigns the serial numbers in accordance with the outbound delivery quantity. If serial numbers have only been specified for a partial quantity of an outbound delivery item, EWM only displays the outbound delivery quantity for serial numbers in inventory management that EWM has assigned serial numbers to. EWM does not display stocks for serial numbers for document items or at warehouse number level. However, if EWM has assigned all serial numbers, or if EWM cannot find any of the predetermined serial numbers, EWM processes the remaining outbound delivery quantity. In such a case, EWM displays the whole stock in accordance with the stock removal process and does not take the partial quantity that EWM has already assigned serial numbers into account.

Only five serial numbers have been specified for outbound delivery item A with ten pieces of product B. The first time you call the use interface for performing a stock removal for an outbound delivery order, EWM only displays the stocks for serial numbers in inventory management on the Stk Can Be Removed tab page. In such a case, EWM displays the stocks for the five predetermined serial numbers, amounting to only five pieces. During the outbound delivery process, EWM creates the corresponding warehouse tasks for the outbound delivery item and reserves these five serial numbers. EWM displays all stocks for product B in the warehouse on the Stk Can Be Removed tab page. You can choose the storage bin from which you want to take the remaining five pieces of product B. When EWM creates a corresponding warehouse task for a warehouse request, EWM determines the necessary location data, handling unit data and stock data for a predetermined serial number. The maximum number of predetermined serial numbers allowed by EWM corresponds to the outbound delivery quantity. If the number of serial numbers in the outbound delivery order is smaller than the outbound delivery quantity, that is, the outbound delivery quantity is not fully serialized, EWM divides the order item internally. EWM creates one or more corresponding warehouse tasks for the fully serialized outbound delivery quantity. EWM also creates a warehouse task for the outbound delivery quantity that is not serialized. (see also Specifying Serial Numbers for Warehouse Task Creation [Seite 599] under ‘Splitting Warehouse Tasks’). If necessary, EWM creates more than one corresponding warehouse task for such an outbound delivery order, for example, if various handling units are necessary for the outbound delivery.

SAP Extended Warehouse Management (SAP EWM)

510

595

SAP Online Help

20.07.2007

Activities If you want to call the user interface for stock removal, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task for Warehouse Request → Stock Removal for Outbound Delivery. If you want to call the user interface for posting changes, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Create Warehouse Task for Warehouse Request → Stock Removal for Posting Change.

SAP Extended Warehouse Management (SAP EWM)

510

596

SAP Online Help

20.07.2007

Using Serial Numbers in a Warehouse Task Use You can work with serial numbers if you or Extended Warehouse Management (EWM) create warehouse tasks, or when you confirm warehouse tasks. If you confirm a warehouse task in the foreground, you can assign serial numbers manually. If you confirm a warehouse task in the background, EWM automatically assigns the serial numbers known to the system. A prerequisite for this is that a complete quant removal occurs and that the serial numbers have been defined.

Features Displaying Serial Numbers You can display the serial numbers in the warehouse management monitor after saving (see Using Serial Numbers in the Warehouse Management Monitor [Seite 604]). On the SAP Easy Access screen, choose Extended Warehouse Management → Monitoring → Warehouse Management Monitor. Select a warehouse task by double clicking it. EWM jumps to the display transaction for warehouse tasks (transaction /SCWM/TO_DISP). EWM displays serial numbers in open, confirmed and archived warehouse tasks. EWM does not display or archive the serial numbers for quantity differences. If you want to display serial numbers from open, confirmed or archived warehouse tasks, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Confirm Warehouse Tasks. Select a warehouse task and display the serial numbers in the detail view for the item on the Serial Numbers tab page.

Confirming Warehouse Tasks ●

If you confirm a warehouse task in the foreground, you can assign serial numbers manually in the following way: ○

From the list of predetermined serial numbers, choose the one which is required. On the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Confirm Warehouse Task and go from the detailed overview for the item to the Serial Number Current Value pushbutton on the Serial Number tab page.

○

Specify a serial number manually. On the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Confirm Warehouse Task and from there, go to the detail view for tab page then Create. Set the Actual indicator the item on the Serial Number for each serial number and manually specify the serial number.

○

If EWM cannot display a list of serial numbers, for example if a product has the serial number requirement Serial Numbers for Document Items or Serial Numbers at Warehouse Number Level, you can assign whole serial number ranges to a warehouse task. On the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Confirm Warehouse Task and go from the detailed overview for pushbutton on the Serial the item to the Serial Number Current Value Number tab page.

SAP Extended Warehouse Management (SAP EWM)

510

597

SAP Online Help

20.07.2007

For more information, see Confirming Warehouse Tasks with Sepcified Serial Numbers [Seite 601] ●

If you want to confirm a difference quantity and you are working with a serial number requirement, you can specify serial numbers for the current value and the difference Serial quantity. You can specify serial numbers for the difference quantity by using Numbers Diff. instead of Actual Serial Number in the detail view for the item or setting the Diff. indicator instead of the Actual indicator for each serial number. Serial Numbers Diff., If you enter differences for a warehouse task, and you select EWM attempts to determine possible predetermined serial numbers and displays them in the input help.

●

Serial Numbers If you are using the warehouse task for the low stock check, select LS instead of Actual Serial Number in the detail view for the item, or set the LS indicator for each serialnumber instead of the Actual indicator.

●

in the overview for If you confirm a warehouse task and use the Check pushbutton the warehouse task, you receive information about whether you have to enter serial numbers. This is dependent on the processing situation, that is, whether you want to specify an exception code or a difference quantity, or you whether you want to work with the low stock check.

●

If you only want to partially confirm a warehouse task and you therefore split the warehouse task, EWM displays the serial numbers that have already been assigned to the warehouse task for the first warehouse task to be split. A prerequisite for this is that you have manually entered the outbound delivery quantity and the serial numbers.

●

If you attempt to confirm a warehouse task without serial numbers, then EWM checks whether serial numbers exist for this warehouse task and, if so, it uses them. If no predetermined serial numbers exist and you carry out a complete stock pick from the storage bin, EWM uses serial numbers that belong to this quant. If no serial numbers exist and you only carry out a partial stock pick from the storage bin, you must confirm the warehouse task in the foreground and enter the serial numbers manually. If you confirm handling units completely, you do not have to enter any serial numbers. An exception occurs if you have implemented the Business Add-In (BAdI) /SCWM/EX_CORE_CO_SN_FORCE in such a way that the user must always enter serial numbers when confirming warehouse tasks.

SAP Extended Warehouse Management (SAP EWM)

510

598

SAP Online Help

20.07.2007

Specifying Serial Numbers for Warehouse Task Creation Use In Extended Warehouse Management (EWM), you can work with predetermined serial numbers in outbound deliveries and posting changes. For example, the ERP system can send serial numbers to EWM in outbound deliveries. If, for example, you use an advanced shipping notification to specify serial numbers in inbound deliveries, EWM does not take the specification from the inbound delivery into account initially. EWM only copies these serial numbers into the corresponding warehouse task once you have confirmed the corresponding warehouse task.

Features When EWM receives serial numbers from another system, it checks whether they are predetermined serial numbers. For inbound deliveries, EWM copies the predetermined serial numbers into the inbound delivery notification and into the outbound delivery request for outbound deliveries. The ERP System sends the predetermined serial numbers to EWM for products with the serial number requirement Serial Numbers for Document Items or Serial Numbers at Warehouse Number Level. EWM copies the predetermined serial numbers into the delivery documents of the inbound and outbound deliveries. However, you must ensure that EWM creates the pick-warehouse task in accordance with the predetermined serial numbers for the outbound delivery order. You must therefore also confirm the storage bin that specifies the respective serial number. The ERP System sends the predetermined serial numbers to EWM for products with the serial number requirement Serial Numbers in Inventory Management. EWM copies the predetermined serial numbers into the delivery documents of the inbound and outbound deliveries. EWM also determines the corresponding location data and handling unit (HU) data for the predetermined serial numbers. EWM needs this data to create corresponding warehouse tasks. If EWM cannot determine this data for the predetermined serial numbers, EWM triggers a pick denial [Seite 327] in the outbound delivery process. While EWM carries out the pick denial, the system determines the serial numbers for which the system could not create warehouse tasks. If you are working with predetermined serial numbers in inbound deliveries, you can manually overwrite these serial numbers. If you are working with predetermined serial numbers in outbound deliveries, you can confirm these serial numbers only. You cannot specify any other serial numbers in the corresponding warehouse task. If EWM displays a warehouse task in display mode, then you can also only display the corresponding serial number.

Executing a Pick Denial If you or EWM carry out a pick denial, EWM saves the serial numbers for the quantity difference in the outbound delivery order. EWM flags unconfirmed serial numbers as invalid. This prevents EWM from creating new warehouse tasks for these serial numbers. You can display the indicator in the outbound delivery order. On the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Outbound Delivery → Maintain Outbound Delivery Order and from there go to the Serial Number tab page in the detail view for the item. The SN Invalid field is selected. Splitting Warehouse Tasks It is possible that EWM may have to split a warehouse task. For example, if the outbound delivery quantity exceeds a certain capacity. EWM splits the warehouse task into two warehouse tasks. One for the allowed outbound delivery quantity and one for the excess SAP Extended Warehouse Management (SAP EWM)

510

599

SAP Online Help

20.07.2007

outbound delivery quantity. EWM reassigns the predetermined serial numbers in accordance with this split and the outbound delivery quantity. EWM also does this for outbound delivery splits that occur during packing (see Integration of the Serial Number in the Delivery [Seite 592] under ‘Delivery Item Split’).

Cancelling Warehouse Tasks If you cancel a warehouse task in the user interface for the outbound delivery request or the outbound delivery order, EWM also deletes the corresponding reservation of predetermined serial numbers and unlocks these serial numbers. EWM does not display these serial numbers in the warehouse task or save them.

SAP Extended Warehouse Management (SAP EWM)

510

600

SAP Online Help

20.07.2007

Confirming Warehouse Tasks with Predetermined Serial Numbers Use If you are working with serial numbers in warehouse tasks, you can confirm these warehouse tasks in the foreground, background or immediately, as in the 'normal' goods issue process.

Features Confirmation in the Foreground If you confirm a warehouse task in the foreground, EWM displays the corresponding predetermined serial number and regards it as your user input. If you want to confirm serial number sin the foreground, on the SAP Easy Access screen, choose Extended Warehouse Management → Execution → Confirm Warehouse Task and then the Confirm in Foreground pushbutton. If you only partially confirm a warehouse task, you can delete the unnecessary serial numbers. To do so, go to the detail view for the item on the Serial Number tab page. If you have implemented Business Add-In (BAdI) /SCWM/EX_CORE_CO_SN_FORCE in such a way that the user must explicitly specify a serial number during confirmation, EWM does not display any predetermined serial numbers. You must then enter these manually, for example by scanning.

Confirmation in the Background If you or EWM confirm a warehouse task with predetermined serial numbers in the background, EWM checks the serial numbers of the warehouse task. If the confirmed serial numbers correspond to the predetermined serial numbers, EWM saves the confirmed serial numbers in the warehouse task and in the corresponding outbound delivery order. You can display these in the outbound delivery order.

Immediate Confirmation If you confirm a warehouse task immediately, EWM uses the serial numbers in the same way as during 'normal' warehouse task creation. EWM checks whether the outbound delivery quantity of the warehouse task is fully serialized. If so, EWM confirms the warehouse task immediately. If serial numbers are only predetermined for a partial quantity in the outbound delivery order, you can only carry out immediate confirmation for warehouse tasks that are either fully serialized or for which EWM can determine the serial numbers. When confirming the warehouse task, you must specify serial numbers for all other warehouse tasks for which EWM cannot fully determine serial numbers (see Warehouse Task Creation with Reference to a Warehouse Request [Seite 595]). If you have implemented the BAdI /SCWM/EX_CORE_CO_SN_FORCE in such a way that the user must enter serial numbers for warehouse task confirmation then EWM cannot confirm the warehouse task immediately. You must create the warehouse task first. When you subsequently confirm the warehouse task, you can specify the required serial numbers.

SAP Extended Warehouse Management (SAP EWM)

510

601

SAP Online Help

20.07.2007

Using Serial Numbers in the Work Center Use You can specify serial numbers at each particular work center. For example, your supplier has not sent serial numbers with the handling units (HUs) you receive. You post the goods receipt for the complete HUs and only specify (by scanning or entering manually) individual serial numbers when you unpack the HUs in the work center.

Prerequisites ●

If necessary, you have set the Assign SNs and Assign SNs to Deliv indicators. In Customizing for Extended Warehouse Management, choose Tab Pages in Scanning Area under Master Data → Work Center → Define Work Center Layout and, if necessary, set the Assign SNos and Assign Snos to Deliv indicators.

●

If necessary, you have set the Serial Numbers indicator. In Customizing in EWM, choose the area General Details under Master Data → Work Center → Define Work Center Layout and, if necessary, set the Serial Numbers indicator.

●

If you want to assign serial numbers at warehouse number level after confirming a pick-warehouse task confirmation to a delivery or an inventory, you need to have posted the goods receipt for the corresponding warehouse for these serial numbers.

Features ●

You can execute the following in the goods receipt process: ○

Assign serial numbers You must enter serial numbers for document items before the goods receipt process. You cannot assign these serial numbers to an inventory or a delivery after the goods receipt posting. You can only assign serial numbers at warehouse number level and in inventory management up until warehouse task confirmation at the final storage bin, that is, until the end of the goods receipt process. You can assign these serial numbers to an inventory as well as a delivery before the goods receipt posting. After the goods receipt posting, you can only assign serial numbers at warehouse number level to one other delivery and, in inventory management, only to one other HU.

○

Delete serial number assignment You can delete the assignment of serial numbers to an inventory or a delivery before the goods receipt posting. If you delete the assignment of serial numbers from the inventory, then they are automatically directly assigned to the delivery. You cannot delete the assignment of serial numbers for document items after the goods receipt posting. You can delete the assignment of serial numbers at warehouse number level to a delivery only after the goods receipt posting. You cannot delete the assignment of serial numbers in inventory management after the goods receipt posting.

●

You can execute the following in the goods issue process: ○

Assign serial numbers

SAP Extended Warehouse Management (SAP EWM)

510

602

SAP Online Help

20.07.2007

You can assign serial numbers for document items and at warehouse number level to a delivery or an inventory after pick-warehouse task confirmation. Serial numbers in inventory management are view-only, as they have already been assigned to an inventory. ○

Delete serial number assignment You can delete the assignment of serial numbers to a delivery or an inventory after pick-warehouse task confirmation. This is only the case for serial numbers for document items or at warehouse number level.

Serial Numbers Without Delivery Reference If you use serial numbers without delivery reference, for example, when you repack stock in the warehouse, you have to specify the serial numbers in inventory management. If you only repack partial quantities, you must also repack the individual serial numbers. Serial numbers for document items and at warehouse number level are not relevant to this process.

Activities If you want to edit serial numbers in the work center, choose, from the SAP Easy Access screen, Extended Warehouse Management → Execution and then one of the following transactions: ●

Packing - General

●

Deconsolidation in Goods Receipt

●

Quality Inspection and Count

●

Create Confirmation for VAS

SAP Extended Warehouse Management (SAP EWM)

510

603

SAP Online Help

20.07.2007

Using Serial Numbers in the Warehouse Management Monitor Use You can display serial numbers in the warehouse management monitor [Seite 878].

Features You can display serial numbers for a physical inventory (the products of which have the serial number requirement Serial Numbers in Inventory Management) in the warehouse management monitor. You can also display Serial Numbers at Warehouse Number Level in the warehouse management monitor. You can only display serial numbers at delivery item level in the delivery document. You can search for the following in the warehouse management monitor: ●

Stock for particular serial numbers To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Monitoring → Warehouse Management Monitor and one of the following nodes in the warehouse management monitor: Search for a stock for a product and a serial number. Select one or more rows. Then select the Serial Numbers pushbutton. The system displays all serial numbers for the selected stock.

●

○

Stock and Bin → Storage Bin → Physical Stock

○

Stock and Bin → Storage Bin → Available Stock → Physical Stock

○

Stock and Bin → Storage Bin → Handling Unit → Physical Stock

○

Stock and Bin → Physical Stock

○

Stock and Bin → Available Stock → Physical Stock

○

Stock and Bin → Resource → Physical Stock

○

Stock and Bin → Resource → Available Stock → Physical Stock

○

Stock and Bin → Handling Unit → Physical Stock

Warehouse tasks for particular serial numbers To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Monitoring → Warehouse Management Monitor → Documents → Warehouse Task and enter the product and the serial numbers.

●

Delivery items for particular serial numbers To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Monitoring → Warehouse Management Monitor → Outbound → Documents → Outbound Delivery Order → Outbound Delivery Order Item or Warehouse Management Monitor → Inbound → Documents → Inbound Delivery → Inbound Delivery Item and enter the serial numbers.

SAP Extended Warehouse Management (SAP EWM)

510

604

SAP Online Help

20.07.2007

Using Serial Numbers in an RF Environment Use You can work with serial numbers in the following Radio Frequency (RF)-supported transactions: ●

Deconsolidation

●

Putaway

●

Picking

●

Packing

●

Counting

Features Entering Serial Numbers Once you have determined the serial number requirement for a product in Customizing, Extended Warehouse Management (EWM) displays this on the RF screen. When you select SNum, EWM displays the entry screen for serial numbers. You can manually specify the necessary serial numbers or scan the barcode in. With this RF display you can also specify the serial numbers in the low stock check or for difference quantities. If you want to delete serial numbers that have already been scanned-in or specified, you have to either scan or specify the barcode for a second time. Subsequently, you delete the serial number using Del.

Displaying Predetermined Serial Numbers If you are working with predetermined serial numbers, EWM assigns them to the corresponding warehouse tasks. If you are in an RF-supported transaction, EWM firstly determines the warehouse tasks and checks whether predetermined serial numbers exist for them. If you select SNum in the RF-supported transaction, EWM displays the predetermined serial numbers. In the RF environment, EWM only displays predetermined serial numbers. You cannot overwrite it. If you only partially confirm an outbound delivery quantity, you must specify the serial numbers manually. EWM does not display any of the predetermined serial numbers.

Entering Serial Number Ranges In the RF environment, you can specify whole serial number ranges instead of individual serial numbers. Select Range on the entry screen for serial numbers. EWM displays a new screen where you can enter the starting and end values for your serial number range. On this screen, EWM also displays the data for the product, the number of serial numbers necessary, and the number of serial numbers that already exist. When you have specified the serial number area, EWM updates the number of existing serial numbers accordingly. EWM displays the serial number range in a step loop and you can then specify the next serial number range. If you want to correct the entry, you must return to the previous screen and make entries again.

SAP Extended Warehouse Management (SAP EWM)

510

605

SAP Online Help

20.07.2007

Serial Numbers for Differences If you specify a difference for an outbound delivery quantity, for example with the exception code DIFW, then you can also specify the corresponding serial numbers. Select SNum on the entry screen for differences. EWM displays the data for the product, the number of serial numbers required, and the number of serial numbers that already exist. If you select List, EWM displays a new screen with all of the existing serial numbers at storage bin, handling unit (HU) and reference document level. The list is only displayed if you have to specify serial numbers for a difference. You can specify one or more row numbers with the serial numbers that you want to select. EWM selects these serial numbers. If you want to undo this operation, re-enter the selected row number. After you have selected one or more row numbers, you can return to the entry screen for serial numbers. EWM displays the selected serial numbers for the difference. When you confirm the corresponding warehouse task, EWM makes a posting change for these selected serial numbers.

Searching for Serial Numbers You can search for serial numbers in the RF environment. To do so, select 05 Internal Processes → 03 Queries → 02 Stock Query → Serial Number Location. Enter the product and serial number. EWM displays the stock or the location for this serial number. You can use HU Det (Handling Unit Detail) to display the detailed data for the HU. You can use BinDe (Bin Detail) to display the data for the stock and for the storage bin.

SAP Extended Warehouse Management (SAP EWM)

510

606

SAP Online Help

20.07.2007

Shipping and Receiving Use The Shipping and Receiving part of Extended Warehouse Management (EWM) comprises the following areas: ●

Loading and Unloading

●

Yard Management

●

Transportation Management

Transportation management is only available for goods issue processes. ●

Route Determination

SAP Extended Warehouse Management (SAP EWM)

510

607

SAP Online Help

20.07.2007

Loading and Unloading Purpose You use this process to load and unload your vehicles [Seite 612] and transportation units [Seite 613] (TUs). For simple loading and unloading processes, you load or unload your deliveries (outbound delivery orders or inbound deliveries) or handling units and thereby automatically trigger a status change. For complex loading and unloading processes [Seite 610], you create warehouse tasks (WTs) and move the handling units into or out of the warehouse. For example, during unloading you bring the goods from the door (source storage bin) to the staging area or to a deconsolidation area or inspection area (destination storage bin). You can post a goods receipt or a goods issue at different times during the loading and unloading process. For example, you can post goods issue without loading, or you can post goods issue after loading. You can post stock receipts and stock issues that result from goods receipts and goods issues to the following inventory management objects: ○

TU (for example, in the yard)

○

Door [Seite 32] (own storage bin)

○

Staging area [Seite 33]

You can post a goods receipt and a goods issue for deliveries and vehicles. Alternatively, you can also post a goods receipt and a goods issue directly into or out of the warehouse.

Prerequisites General Information ●

Outbound delivery orders or inbound deliveries have been created automatically in Extended Warehouse Management (EWM) for deliveries from SAP R/3.

●

You have created handling units. These are a prerequisite for complex loading and unloading processes.

●

You have made the settings for storage control in Customizing for EWM. For example, you must define storage types for staging area groups (also called goods receipt or goods issue areas) and doors. These settings are necessary for complex loading and unloading processes.

Vehicles and TUs ●

You have defined TUs, vehicles, and default owners in the master data (to do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Shipping and Receiving).

●

You have defined a means of transport in Customizing for SAP Advanced Planning and Optimization (SAP APO) under Master Data → Transportation Lane → Define Means of Transport.

●

You have made the settings for vehicles and TUs in Customizing for EWM under Cross-Process Settings → Shipping and Receiving, for example: ○

Number ranges

○

Settings for the Post Processing Framework (PPF)

SAP Extended Warehouse Management (SAP EWM)

510

608

SAP Online Help ○ ●

20.07.2007

Control parameters for forming vehicles and TUs

You have defined links between packaging materials (TUs) and means of transport (to do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Settings → Shipping and Receiving).

Staging Area and Door Determination You have set up staging area and door determination [Seite 615].

Process Simple Loading Process 1. The picked outbound delivery orders or handling units, if you have directly picked in handling units, are ready to be loaded, for example, in the goods issue area. 2. You load the outbound delivery orders (transaction /SCWM/LOAD). When saving, the system updates the status of the outbound delivery orders and HUs. Variant with vehicles and TUs You can load multiple outbound delivery orders for the vehicle (transaction /SCWM/VEH) or for the TUs (transaction /SCWM/TU). Here the system also updates the status when saving. 3. You post the goods issue for the outbound delivery orders (transaction /SCWM/LOAD). Variant with vehicles and TUs You can also post the goods issue for the vehicle (transaction /SCWM/VEH) or for the TUs (transaction /SCWM/TU). 4. At the end of loading, at the latest when you post goods issue, the system automatically creates outbound deliveries for the relevant outbound delivery orders. Simple Unloading Process ... ...

1. You receive advanced shipping notifications (ASNs) that give you an overview of the workload to be expected. Variant with vehicles and TUs The vehicle drives into the yard. You register or enter the vehicle (transaction /SCWM/VEH) or the TUs (transaction /SCWM/TU), and set the Arrival at Checkpoint status. You can post the goods receipt for the vehicle (transaction /SCWM/VEH) or the TUs (/SCWM/TU) immediately, in other words, before you have unloaded the vehicle. 2. You unload the inbound deliveries and post the goods receipt (transaction /SCWM/UNLOAD). When saving, the system updates the status of the inbound deliveries and HUs. Variant with vehicles and TUs You unload the inbound deliveries for the vehicle (transaction /SCWM/VEH) or for the TUs (transaction /SCWM/TU). Here the system also updates the status when saving. 3. The goods are ready for the final putaway in the goods receipt area, for example. See also: Assignment of Deliveries to Vehicles and TUs [Seite 617] Integration of TM with the Loading Process [Seite 635]

SAP Extended Warehouse Management (SAP EWM)

510

609

SAP Online Help

20.07.2007

Complex Loading and Unloading Purpose In the case of complex loading and unloading processes, you create warehouse tasks (WTs) and move the products into or out of the warehouse. Complex loading and unloading processes are based on the storage control [Seite 334] settings that the system uses to determine the destination storage bin for a WT. Complex loading and unloading processes run in the same way as any other WT processing when warehouse orders are created [Seite 419]. For this reason, the following describes only the special features of these two processes.

Prerequisites See Loading and Unloading [Seite 608].

Process Loading When you confirm an internal WT within the warehouse, the system can automatically create the next WTs on the basis of storage control. The latter WT is called the loading WT. You can also manually create and confirm this loading WT. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Goods Receipt and Shipping → Load. Alternatively, the creation of the loading WT can be triggered automatically by a status change when the TU arrives at the door. This occurs via a PPF action (PPF = Post Processing Framework). The system creates loading WTs with the default destination storage bin Door. If a WT is confirmed at a door where a TU is positioned, the system automatically changes the destination storage bin in the WT to TU. Ad hoc movements [Seite 415] are the exception to this rule. You can use loading rules to influence the time of loading. In this way, you can specify, for example, that loading is not to start until 24 hours after you have confirmed the WT with the destination storage bin Staging Bay. You choose loading rules when defining staging areas. Unloading The unloading process runs in the same way. Here, however, the system posts goods issue at the latest after the unloading WT has been confirmed.

SAP Extended Warehouse Management (SAP EWM)

510

610

SAP Online Help

20.07.2007

Loading and Unloading Using Radio Frequency Use You can also execute loading and unloading using a radio frequency presentation device (RF presentation device).

Prerequisites ●

You have logged on [Seite 790] in the RF environment.

●

You have defined a warehouse order creation rule of the type Load/Unload and have specified the number of loading employees who are to execute the higher-level warehouse order in Customizing for Extended Warehouse Management (EWM) under Cross-Process Settings → Warehouse Order → Define Creation Rule for Warehouse Orders.

Features You can use this function to have multiple loading employees load or unload a transportation unit [Seite 613], even if the entire transportation unit corresponds to only one warehouse order. In this case, the system creates a higher-level warehouse order that contains all WTs for the HUs of the transportation unit.

Activities The following describes an example of unloading a truck with four HUs and two loading employees. Loading works in the same way. 1. When the system finds a warehouse order creation rule of the type Load/Unload, it creates a higher-level warehouse order with four WTs. 2. In accordance with the warehouse order creation rule, the system creates two warehouse orders for the two loading employees who are to unload the HUs. These two warehouse orders are linked to the higher-level warehouse order, but do not have any WTs. 3. The system transfers the two warehouse orders as executable to resource management. They are now ready to be processed in the RF environment. 4. The system transfers the two warehouse orders to the two loading employees. They go to the relevant trucks (in accordance with the warehouse order). 5. As soon as the two loading employees scan the first HU, the system automatically moves the relevant WT from the higher-level warehouse order to the warehouse order belonging to the relevant loading employee. 6. Both loading employees unload all the HUs and confirm the corresponding WTs. The higher-level warehouse order no longer contains any WTs, since the system has distributed them to the lower-level warehouse orders. After the loading employees have confirmed the last WT, all warehouse orders involved are completed (in other words, confirmed or canceled). This would also be the case, even if only one loading employee had unloaded the truck.

SAP Extended Warehouse Management (SAP EWM)

510

611

SAP Online Help

20.07.2007

Vehicle Definition A specialization of a particular means of transport. A vehicle can comprise one or more transportation units [Seite 613].

Use You define vehicles in the master data for transportation. You use vehicles to group deliveries and to communicate with invoicing and Transportation Management (TM) [Seite 629]. If you assign transportation units to a vehicle in a fixed way, you cannot assign these transportation units to another vehicle. In this case, data that you define for the vehicle is also valid for the assigned transportation units. The dimensions of the vehicle come from the means of transport that you assign to the vehicle, and are used as the planned size.

Integration ●

When the loading process has been completed, a status change triggers the sending of a message to TM that enables bills of lading to be created automatically (see Integration of TM with the Loading Process [Seite 635]).

●

Before goods issue posting, you can create the current invoice via an invoice request to SAP CRM Billing (see Invoice Creation Before Goods Issue [Seite 368]).

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

SAP Extended Warehouse Management (SAP EWM)

510

612

SAP Online Help

20.07.2007

Transportation Unit Definition The smallest loadable unit of a vehicle [Seite 612] that is used to transport goods. The transportation unit (TU) can be a fixed part of the vehicle. The following figure shows different transportation units: ●

Vehicle 1: Semitrailer truck with one transportation unit

●

Vehicle 2: Truck with cargo area and trailer, in other words, two transportation units

●

Vehicle 3: Train with four wagons, in other words, four transportation units Transportation Unit 1

Vehicle 1

Vehicle 2

Transportation Unit 1

Transportation Unit 2

Vehicle 3 TU 1

TU 2

TU 3

TU 4

You map transportation units as handling units (HUs) and assign packaging materials to them. By linking these packaging materials to means of transport, you define construction rules for your vehicles. In this way, you define, for example, how many transportation units a vehicle is supposed to have and the order in which they are to be arranged. You also specify whether a transportation unit is to be optional or obligatory: ●

Obligatory transportation units are a fixed part of a vehicle (fixed assignment). You cannot assign them to another vehicle, for example, truck cargo area.

●

You can assign optional transportation units to other vehicles, for example, trailer for a truck.

Use You define transportation units in the master data for transportation. You use them for inventory management in the yard.

Example The following are additional examples of transportation units: ●

Compartment in a tank truck

●

Container

SAP Extended Warehouse Management (SAP EWM)

510

613

SAP Online Help

20.07.2007

Creating Vehicles and Transportation Units Use You must perform the following steps to be able to create vehicles and transportation units in the following transactions: ●

Maintain Vehicle (/SCWM/VEH)

●

Maintain Transportation Unit (/SCWM/TU)

●

Arrival at/Departure from Checkpoint (/SCWM/CICO)

Procedure 1. Create a means of transport. To do so, on the SAP Easy Access screen, choose Advanced Planning and Optimization → Master Data → Transportation Lane → Maintain Means of Transport. 2. Define number ranges for vehicles, TUs, and shipping and receiving activities. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Shipping and Receiving → Number Ranges. 3. Define whether the means of transport is relevant to shipping and receiving (assignment as TU, vehicle, or both) and define additional parameters, for example, number ranges and action profile. For more information, see the IMG for EWM under Cross-Process Settings → Shipping and Receiving → General Settings → Define Control Parameters for Forming Vehicles/Transportation Units. 4. Define a packaging material type with the packaging material category A (Means of Transport, Transport Element, Transport Unit). For more information, see the IMG for EWM under Goods Receipt Process → Slotting → Influencing Parameters → Packaging Material Determination → Define Packaging Material Types. 5. Create a packaging material with the packaging material type defined previously. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Product → Maintain Product. 6. Link the packaging material to the means of transport. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Settings → Shipping and Receiving → Link Between Packaging Material (TU) and Means of Transport. 7. Define a default owner. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Shipping and Receiving → Default Owners of Transportation Units and Vehicles.

SAP Extended Warehouse Management (SAP EWM)

510

614

SAP Online Help

20.07.2007

Staging Area and Door Determination Use In staging area and door determination, the system can determine the following values by using determination rules: ●

Staging area groups

●

Staging areas [Seite 33]

●

Staging bays

●

Doors [Seite 32]

The system needs staging areas, staging area groups, and staging bays for storage control [Seite 334]. Staging area and door determination runs automatically in the background when you create or change a delivery (outbound delivery order or inbound delivery) in Extended Warehouse Management (EWM). In the outbound delivery process, it runs after route determination [Seite 638] since the route influences the determination of staging areas and doors.

Integration Integration with delivery processing is necessary for using staging area and door determination.

Prerequisites •

You have defined staging area/door determination groups in Customizing for EWM under Master Data → Staging Areas.

•

You have defined doors and assigned staging areas and staging area/door determination groups to these doors in Customizing for EWM under Master Data → Warehouse Door.

●

You should not specify a staging area or a door as the destination storage type/destination storage bin when defining the warehouse process type for the delivery in Customizing for EWM under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type.

Features In order that the system can perform staging area and door determination in the background, you must define determination rules. When doing this, you first specify which values the system is to compare with the values in the delivery: ●

Inbound delivery process: Warehouse process type and staging area/door determination groups

●

Outbound delivery process: Routes, departure calendar, staging area/door determination groups, and destination sequence numbers

You then define which of the values named under Use are to be determined by the system.

If, in a radio frequency scenario, you specify a staging area group but no staging area or staging bay, the first handling unit (HU) that you confirm for a staging area defines the staging areas and staging bays for all additional HUs.

SAP Extended Warehouse Management (SAP EWM)

510

615

SAP Online Help

20.07.2007

When the system performs staging area and door determination, it checks the determination rules one after another until it finds one whose values match the values of the delivery in question. It then writes the values defined for this determination rule into the delivery.

Activities To define the determination rules for staging area and door determination, on the SAP Easy Access screen, choose Extended Warehouse Management → Settings → Shipping and Receiving → Staging Area and Door Determination (Inbound) or Staging Area and Door Determination (Outbound).

SAP Extended Warehouse Management (SAP EWM)

510

616

SAP Online Help

20.07.2007

Assignment of Deliveries to Vehicles and TUs Use Every delivery maps a one-off business event and is represented in the system by a unique document. You can reuse vehicles and transportation units (TUs), on the other hand, as many times as you want to. If, however, you want to make vehicles and TUs unique, you use shipping and receiving activities [Seite 624] (S&R activity). You can manually assign every delivery to a TU and S&R activity in the transaction Maintain Transportation Unit (/SCWM/TU). You can also automatically assign deliveries to TUs using advanced shipping notifications. In both cases, the system copies the external vehicle number into the delivery when either you or the system assign this delivery to a TU that is assigned to a vehicle.

SAP Extended Warehouse Management (SAP EWM)

510

617

SAP Online Help

20.07.2007

Printer and Form Determination in Shipping and Receiving Use You can use printer and form determination to control which printer is used and which type of form is to be printed.

Features Printer determination You can use criteria to define which printer is to be used. If you do not define any criteria, the printer that you have specified in the user profile in your system is used automatically. Printer determination is the same for transportation units (TUs) and vehicles.

Form determination For automatic printing, you can use criteria to specify which form, in other words, which Smart Form, is to be printed.

You can print freight lists on a carrier-specific basis. A separate form determination is available for TUs and vehicles.

By default, form determination via the Post Processing Framework (PPF) is used.

Activities To configure printer and form determination, on the SAP Easy Access screen, choose Extended Warehouse Management → Settings → Shipping and Receiving → Configure Printer and Form Determination.

SAP Extended Warehouse Management (SAP EWM)

510

618

SAP Online Help

20.07.2007

Yard Management Use You use Yard Management to manage your yards [Seite 621]. The yard is where you maintain vehicles [Seite 612] and transportation units [Seite 613] that arrive or depart. You map movements within a yard using warehouse tasks (WTs). For more information, see Yard Movement [Seite 626]. You can monitor your yard in the warehouse management monitor [Seite 878]. The following figure shows an example of a yard.

Door A1 Space 17

Door A2

Warehouse 0001

P00A

Door An

Checkpoint I

Door Y1

Door B1

Door Bn

Door Yn

Door X1

Warehouse 000n Door X2 Door Xn

Space 34

P00B Checkpoint II

Integration Yard management is integrated into SAP Global Trade Services (GTS). For more information about GTS, see the SAP Library under SAP xAPPs → SAP Global Trade Services.

Prerequisites ●

You have activated yard management for the warehouse in Customizing for Extended Warehouse Management (EWM) under Cross-Process Settings → Shipping and Receiving → Yard Management → Activate Yard Management for Warehouse.

●

You have made the following settings in Customizing for EWM under Master Data → Shipping and Receiving → Yard Management:

●

○

You have defined the yard using the storage type.

○

You have defined checkpoints [Seite 622].

○

You have optionally structured the yard using storage sections.

You have defined doors [Seite 32] in Customizing for EWM under Master Data → Warehouse Door → Define Warehouse Door.

SAP Extended Warehouse Management (SAP EWM)

510

619

SAP Online Help ●

20.07.2007

You have assigned the doors and checkpoints to yard bins. You have also specified a warehouse process type for the checkpoints. These are required by the system for the arrival at and departure from the checkpoint. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Shipping and Receiving → Yard Management → Assign Warehouse Door to Yard Bin or Assign Checkpoint to Yard Bin and SCU.

See also: Arrival at/Departure from Checkpoint [Seite 623] Connection of Delivery Processing to Yard Management [Seite 199]

SAP Extended Warehouse Management (SAP EWM)

510

620

SAP Online Help

20.07.2007

Yard Definition An enclosed area outside a warehouse where vehicles and transportation units are dealt with, waiting to be dealt with, or waiting to be collected by an external carrier.

Structure A yard is based on the warehouse structure [Seite 21] of Extended Warehouse Management (EWM). A yard represents a separate storage type in a warehouse. However, you can also configure it with a separate warehouse number, which must then include a storage type that has the role Yard. In both cases, you can use one yard for multiple warehouses. Conversely, you can define a warehouse with multiple yards. You map the corresponding storage bins as yard bins, which you can group into yard sections, the same as for the warehouse. The following are possible types of yard bin: ●

Parking spaces [Extern] You map parking spaces as standard storage bins with standard storage sections and standard storage bin types.

●

Checkpoints [Seite 622]

●

Doors [Seite 32] The door connects the yard to the warehouse. It is important for stock posting and yard movements.

You can group yard bins into yard sections. The following figure shows a yard that has been defined as a separate storage type. Warehouse number 0001 ST: STAG. AREA

ST: YARD

SS: CPNTA Checkpoint A

ST: DOOR

SS: 0003

SS: 0001

SS: 0001

Storage Bin

SS: 000n SS: 0002

Storage Section (SS) Storage Type (ST)

SS: CPNTB

Door

Checkpoint B

SAP Extended Warehouse Management (SAP EWM)

510

621

SAP Online Help

20.07.2007

Checkpoint Definition Location where vehicles and transportation units (TUs) arrive at or leave the yard. This can represent a physical gate at the yard entrance, or a virtual gate from which data is transmitted electronically.

Use The checkpoint is where you register the arrival of vehicles and TUs in the yard and their departure from it. For more information, see Arrival at/Departure from Checkpoint [Seite 623].

Structure You map checkpoints using Yard Bins [Extern]. You must assign each checkpoint to a yard bin. This assignment must be unique, meaning you cannot assign two checkpoints to the same yard bin. You must also assign each checkpoint to a Supply Chain Unit [Seite 53] (SCU), such as the SCU of the warehouse.

SAP Extended Warehouse Management (SAP EWM)

510

622

SAP Online Help

20.07.2007

Arrival at/Departure from Checkpoint Purpose The checkpoint is where you register the vehicles and transportation units (TUs) that arrive in or leave the yard, by setting the status for the arrival at the checkpoint or departure from the checkpoint. Registering vehicles and TUs that arrive in the yard is a prerequisite for Yard Movements [Seite 626].

Prerequisites See Yard Management [Seite 619].

Process The exact steps you execute at the checkpoint depend on whether you have obtained the vehicle data and transportation unit data in advance through advanced shipping notification, for example, or whether you first have to record this when the vehicle has arrived.

Data is already available In the function Arrival at/Departure from Checkpoint, you set the status Arrival at Checkpoint fort he vehicle. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Goods Receipt and Shipping → Yard Management → Arrival at/Departure from Checkpoint (Transaction /SCWM/CICO).

Data has to be recorded 1. You create the vehicle in the system (transaction /SCWM/CICO or /SCWM/VEH). 2. You create a TU if required and assign it to the vehicle. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Goods Receipt and Shipping → Maintain Transportation Unit (/SCWM/TU). 3. You register the arrival of the vehicle by setting the status Arrival at Checkpoint (transaction /SCWM/CICO or /SCWM/VEH). 4. You register the TUs (transaction /SCWM/TU). In the following cases, you can also post the arrival at checkpoint in this transaction right away: ○

TU is not assigned to a vehicle

○

TU is assigned to a vehicle that contains just one TU

Otherwise you have to post the arrival at checkpoint in transaction /SCWM/VEH. 5. You assign deliveries and handling units to the TUs (transaction /SCWM/TU).

SAP Extended Warehouse Management (SAP EWM)

510

623

SAP Online Help

20.07.2007

Shipping and Receiving Activity Definition Period in which an object is used in a particular context: ●

Goods receipt or goods issue of a transportation unit (TU)

●

A vehicle’s stay in the yard

●

Loading or unloading process of a door

A shipping and receiving activity (S&R activity) is unique for each object and time.

Use You use shipping and receiving activities to uniquely identify vehicles, TUs, and doors for a particular time period, thus enabling unlimited use.

Structure Each shipping and receiving activity has a unique identification (ID), planned time, and actual time: •

Planned start date/time period (such as 23.11.05 between 10:00 and 11:00)

•

Actual start date/time (such as 23.11.05 at 10:30)

•

Planned finish date/time period

•

Actual finish date/time

A shipping and receiving activity can have one of the following statuses: •

Planned

•

Active

•

Completed

•

Invalidated (canceled)

Only one active S&R activity is possible per object (vehicle, TU, or door). The system considers this first of all when it executes activities for the respective object. Activities for planned and completed S&R activities are also possible, such as archiving or deleting. Information about S&R activities in connection with the individual objects: ●

●

S&R activities for vehicles ○

You or the system create a new planned S&R activity for a vehicle, when its arrival in the yard has been planned.

○

The status of the S&R activity for a vehicle changes from Planned to Active when the status of the vehicle changes to Arrival at Checkpoint.

○

The status of the S&R activity for a vehicle changes from Active to Completed when the status of the vehicle changes to Departure from Checkpoint.

S&R activities for TUs ○

You or the system create a new planned S&R activity for a TU when its arrival in the yard has been planned, or, at the latest, when you or the system assign TU deliveries (inbound or outbound).

SAP Extended Warehouse Management (SAP EWM)

510

624

SAP Online Help

20.07.2007

○

The status of the S&R activity for a TU changes from Planned to Active when the status of the TU changes to Arrival at Checkpoint. You can also change the status manually using the function Maintain Transportation Unit (/SCWM/TU).

○

The status of the S&R activity for a TU changes to Completed when the status of the TU changes to Departure from Checkpoint.

If you want to use a TU during its stay in the yard for both an inbound and an outbound process, you map this using two S&R activities. In this instance, you can use function /SCWM/TU to change the status of the completely unloaded inbound S&R activity from Active to Completed, and the status of the new S&R activity from Planned to Active, without having to post the arrival at or departure from the checkpoint. ●

S&R activities for doors ○

You or the system create a new planned S&R activity for a door when you or the system assign a TU to the door.

○

The status of the S&R activity for a door changes to Active when the TU arrives at the door.

○

The status of the S&R activity for a door changes to Completed when the assigned TU leaves the door.

SAP Extended Warehouse Management (SAP EWM)

510

625

SAP Online Help

20.07.2007

Yard Movement Use Yard movements enable you to move transportation units [Seite 613] (TUs) from one yard bin [Extern] to another inside a yard. Possible types of yard movement are as follows: ●

The TU arrives at the checkpoint and is moved to a parking space or to the door.

●

You move a TU from a parking space to the door, or from the door to a parking space.

●

You move a TU within the yard, from one parking space to another, or from one door to another.

You map each TU using an empty handling unit (HU) which is described as a HU for the TU and is moved during the yard movement.

Prerequisites See Yard Management [Seite 619]. For you to be able to move TUs in the yard, the following conditions must be fulfilled: ●

You have posted goods receipt for the HU for the TU (for arrival at the checkpoint).

●

The TU must have the status Active (for arrival at the checkpoint).

Features Each time you want to move a TU in the yard, you have to create a warehouse task (WT) [Seite 405] manually. To do this, you use the standard functions for creating and confirming WTs. The following figure shows the relationship between a TU and the relevant HU for the TU. This relationship is 1:1.

ƒ Empty HU for TU for all yard movements 1:1

Transportation Unit (TU)

Pack. Material

ƒ Stock = Packaging material HU for TU

Product A Whse S1

Pack. Material

Product A Whse S1

Product B Whse S2

ƒ Stock overview in yard via TU only

Deliveries assigned to the TU

Product B Whse S2

For yard movements, the HU for the TU always remains empty, meaning you can never pack the contents of the TU (deliveries with HUs and unpacked products) into an HU for the TU. If you move the HU for the TU in the yard, the system considers only the packaging material, that is, the HU, from a stock point of view, whereas the related stock does not follow every movement.

SAP Extended Warehouse Management (SAP EWM)

510

626

SAP Online Help

20.07.2007

WTs for yard movements are always HU WTs. The system does not use product WTs because quantities are not considered in yard movements. For more information about HU WTs and product WTs, see Ad Hoc Movement [Seite 415].

Activities To create and confirm a WT for a yard movement, on the SAP Easy Access screen, choose Extended Warehouse Management → Goods Receipt and Shipping → Yard Management → Create Warehouse Task in Yard (/SCWM/YMOVE). To get an overview of the situation in the yard, you can use the warehouse management monitor [Seite 878]. You can also display stock for TUs there. To display for example delivery items or deliveries that are assigned to the TU, you can use the transaction Maintain Transportation Unit (/SCWM/TU).

SAP Extended Warehouse Management (SAP EWM)

510

627

SAP Online Help

20.07.2007

Yard Movement Using Radio Frequency Use You can also execute yard movements in a radio frequency (RF) environment.

Prerequisites You have logged on [Seite 790] in the RF environment.

Activities Create Warehouse Task ...

1. Scan the transportation unit (TU) and specify the standard carrier alpha code (SCAC) or carrier. The system creates a warehouse task (WT) for the handling unit that is assigned to the TU. 2. Confirm the WT on the desktop.

Create and Confirm Warehouse Task ... ...

1. Scan the transportation unit (TU). The system creates a warehouse task (WT) for the handling unit that is assigned to the TU. 2. Confirm the WT by scanning the destination storage bin.

SAP Extended Warehouse Management (SAP EWM)

510

628

SAP Online Help

20.07.2007

Transportation Management in EWM Use Extended Warehouse Management (EWM) has its own Transportation Management (TM) area. The following sections describe the functions available as well as the integration of TM with Shipping and Receiving.

SAP Extended Warehouse Management (SAP EWM)

510

629

SAP Online Help

20.07.2007

Shipment Definition Document containing all the goods that are consolidated by a ship-from party and are then transported together from an issuing location (a plant, for example) to a destination location (a customer, for example). The shipment forms the basis for planning, executing, and monitoring the transportation of goods.

Use You can create shipments both manually and automatically. A shipment can have different characteristics that are determined by the shipment type as well as its relationship to other shipments. You define the shipment type in Customizing for Transportation Management (TM). It contains all the important control parameters for the shipment document. The following table shows the possible instances of shipments, the required settings, and the usages: Instance Transportation request

Bill of lading

Settings ●

In Customizing for TM under Define Shipment Type, you have not set the UI Changeable indicator for the shipment types Planned Transportation Request and Final Transportation Request.

●

In Customizing for TM under Maintain Settings for Determining Shipment Types, you have defined the shipment types Planned Transportation Request and Final Transportation Request as predecessor shipment types.

●

In Customizing for TM under Define Shipment Type, you have set the UI Changeable indicator for the shipment type Bill of Lading.

●

In Customizing for TM under Maintain Settings for Determining Shipment Types, you have defined the shipment type Bill of Lading as a successor shipment type.

Use You can assign transportation requests to bills of lading or to freight documents.

●

●

SAP Extended Warehouse Management (SAP EWM)

You can assign transportation requests with common properties to a bill of lading, for example: ○

Transportation service provider

○

Ship-from party and ship-to party

○

Delivery date

You can manually set statuses in the bill of lading, for example, Transportation Completed. In this case, the relevant paper document (international bill of lading (CMR) or bill of lading according to VICS standard) is printed automatically. For more information about printing,

510

630

SAP Online Help

20.07.2007 see Post Processing Framework [Extern].

The following classification is relevant to the processes in the Extended Warehouse Management (EWM) component: ●

Planned shipment: Can still change with regard to type and size, for example, due to a subsequent delivery split in the Extended Warehouse Management (EWM) component.

●

Final shipment: Is fixed with regard to type and size, in other words, it is confirmed. Most of these shipments are already packed or loaded.

Structure The header contains data such as: ●

Incoterms

●

Partners

●

Dates/times

●

Transportation details such as transportation mode, route, stops, and transit direction

The shipment items contain data such as locations, dates/times, packages, products, weight and volume, units of measure, and references to the original document, for example, the delivery.

Integration The automatic creation of shipments occurs via an integration interface with goods accepted and shipping. You can also communicate shipments using IDocs. The IDoc structure of the freight document is compatible with the EDIFOR standard (subset of EDIFACT [Extern]) IFCSUM (International Forwarding and/or Transport Message Consolidation Summary). See also: Freight Document [Seite 632] Creation of Freight Documents [Seite 633]

SAP Extended Warehouse Management (SAP EWM)

510

631

SAP Online Help

20.07.2007

Freight Document Definition Document that reflects the result of planning and consolidating shipments [Seite 630] and that is used in collective goods traffic, for example. The freight document determines the load on a vehicle.

Use The freight document is relevant to transferring planning results and to printing, and maps trips as well as multiple pickups and stops. You can create freight documents both manually and automatically. You define the freight document type in Customizing for Transportation Management (TM). It contains all the important control parameters for the freight document. You can manually set statuses in the freight document, for example, Transportation Completed. In this case, this status is set automatically for all the bills of lading contained in the freight document. These are then printed automatically. You can also print master bills of lading [Extern] and freight lists [Extern] from the freight document. For more information about printing, see Post Processing Framework [Extern].

Structure The freight document contains data such as: ●

Transportation details (for example, route, transportation mode)

●

Business partners

●

Status

●

Dates/times (for example, loading date, pickup, arrival)

●

Loading or unloading sequence

●

Reference documents

Integration The automatic creation of freight documents occurs using an IDoc. Changes that you have made manually or changes that were communicated using an IDoc (such as changed dates/times, transportation details, or statuses) are transferred automatically to the shipments contained in the freight document. If you set the status Transportation Completed, for example, in the freight document, it is also set automatically for all shipments contained in the freight document. The IDoc structure of the freight document is compatible with the EDIFOR standard (subset of EDIFACT [Extern]) IFCSUM (International Forwarding and/or Transport Message Consolidation Summary). The creation of freight documents can also be triggered from the Shipping and Receiving area by sending a final load message or a load message to TM. Both of these messages are also compatible with the EDIFOR standard IFCSUM. For more information about creating freight documents, see Creation of Freight Documents [Seite 633].

SAP Extended Warehouse Management (SAP EWM)

510

632

SAP Online Help

20.07.2007

Creation of Freight Documents Use You can create freight documents [Seite 632] in different ways. Freight documents reflect the result of planning and consolidating shipments [Seite 630]. They are used as the basis for creating loads on vehicles.

Prerequisites ●

You have defined the following in Customizing for Transportation Management (TM): ○

Transportation planning points

○

Settings for transportation planning point determination and assignment to an external transportation planning system (TPS), if you want to use an external TPS

○

Shipment types and freight document types

○

Settings for shipment type determination, if you want to use your own document types, and settings for freight document type determination

Features You can create freight documents in the following ways: ●

If you have connected an external transportation planning system (TPS), the planned shipments are sent automatically via IDoc to this TPS. In the TPS, you plan the transportation; for example, you can group shipments that are to be transported with the same vehicle or you can change dates/times. The result of transportation planning is a freight document. This is sent back automatically to Transportation Management (TM). If the vehicle is not yet known in shipping and receiving, a vehicle, a transportation unit (TU), and a vehicle activity are automatically created there. You can maintain the freight document in TM. For example, you can change transportation details such as the means of transport or the dates/times. The relevant shipments, deliveries, and vehicles are updated automatically.

●

If you have not connected an external TPS, you create the freight document manually in TM. When doing this, you group multiple planned shipments that are to be or can be transported together. To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Goods Receipt and Shipping → Transportation → Maintain Freight Document. If the vehicle is not yet known in shipping and receiving, a vehicle, a transportation unit (TU), and a vehicle activity are automatically created there.

●

If deliveries have already been assigned to vehicles or transportation units (TUs) in shipping and receiving, a freight document is automatically created or updated via a message in TM. The system also automatically updates assignments between shipments and freight documents and sets the status Planning Fixed by Execution. You must not change the documents in TM. The data merely serves as a source of information and as a prerequisite for the automatic creation of bills of lading and for printing. In this case, the following paragraph is not relevant.

After a freight document has been created, the relevant shipments and deliveries are automatically updated with the planned transportation data, for example, vehicle. The outbound delivery orders get the status Transportation Planning End.

SAP Extended Warehouse Management (SAP EWM)

510

633

SAP Online Help

20.07.2007

See also: Loading and Unloading [Seite 608] Integration of TM with the Loading Process [Seite 635]

SAP Extended Warehouse Management (SAP EWM)

510

634

SAP Online Help

20.07.2007

Integration of TM with the Loading Process Purpose By integrating Transportation Management (TM) with the Extended Warehouse Management (EWM) component, you enable bills of lading to be printed automatically when vehicles are being loaded.

Prerequisites You have set up printer and form determination. For more information, see Printer and Form Determination [Seite 636].

Process ...

1. When an outbound delivery or an outbound delivery order is created or changed in delivery processing, a notification is automatically sent to TM. In TM, planned shipments [Extern] or final shipments [Extern] are created or updated. 2. When deliveries are assigned to transportation units and vehicles in shipping and receiving, and the status Loading End is set, a notification is sent to TM. Bills of lading are created automatically in TM and the status Shipment Completed is set. Bills of lading are an aggregation of final shipments that are assigned to a freight document [Seite 632]. Provided that a freight document from earlier planning results is not already available, a freight document is automatically created on receipt of this notification. For more information, see Creation of Freight Documents [Seite 633]. 3. The bills of lading are automatically printed in accordance with the CMR or VICS standards. You determine which type of bill of lading is printed in printer and form determination [Seite 636]. For more information about printing, see Post Processing Framework [Extern].

■

You can use the Business Add-In (BAdI) /SCTM/EX_BOM to change the criteria by which final shipments are grouped during the automatic creation of bills of lading. By default, the system groups the shipments by ship-from party and ship-to party.

■

To create bills of lading, you have the following alternative options: ○

In the transaction Maintain Freight Document (/SCTM/FRD), you can trigger the automatic creation of bills of lading using the Create Bill(s) of Lading pushbutton.

○

In the transaction Maintain Shipment (/SCTM/SHP), you can create bills of lading manually and assign final shipments to them which, for example, share the same route or ship-to party. You can also create new bill of lading items. You can then manually set the status Shipment Completed for these bills of lading.

See also: Loading and Unloading [Seite 608]

SAP Extended Warehouse Management (SAP EWM)

510

635

SAP Online Help

20.07.2007

Printer and Form Determination in Transportation Management Use You can use printer and form determination to control which printer is used and which type of form is to be printed.

Features Printer determination You can use criteria to define which printer is to be used. If you do not define any criteria, the printer that you have specified in the user profile in your system is used automatically. Printer determination is the same for bills of lading and freight documents.

Form determination For automatic printing, you can use criteria to specify which form, in other words, which Smart Form, is to be printed.

You can print bills of lading based on the country of origin or country of destination, or in accordance with the CMR or VICS standard. A separate form determination is available for freight documents and bills of lading.

By default, form determination via the Post Processing Framework (PPF) [Extern] is used. In Customizing for Transportation Management, you can define the PPF action with a fixed form. To do so, choose Extended Warehouse Management → Goods Issue Process → Transportation Management → Basics → Define PPF Action Profiles and Define PPF Conditions.

Activities To configure printer and form determination, on the SAP Easy Access screen, choose Extended Warehouse Management → Settings → Shipping and Receiving → Transportation → Printer and Form Determination. You must configure the following: ●

Form determination for bills of lading

●

Form determination for freight documents

●

Printer determination for Transportation Management

●

Print profile for Transportation Management

SAP Extended Warehouse Management (SAP EWM)

510

636

SAP Online Help

20.07.2007

Authorizations in Transportation Management Use In the area of Transportation Management (TM), you use the SAP authorization concept [Extern] to control access to applications. For more information about the authorization function, see Users and Roles (BC-SEC-USR) [Extern] and Checking Authorizations [Extern].

Features The following table shows the authorization objects available in TM. For more information, see the relevant system documentation. Authorization Object

Description

/SCTM/AUTH

General authorizations for transportation

/SCTM/STAT

Authorizations for transportation status

SAP Extended Warehouse Management (SAP EWM)

510

637

SAP Online Help

20.07.2007

Route Determination Use The aim of route determination is to find the most cost-effective route from a large number of routes. Route determination is executed in the routing guide. It runs automatically in the background, for example, when a Global Available-to-Promise (Global ATP) check is performed in SAP Customer Relationship Management (SAP CRM) during the creation of a sales order. A report is available for simulating route determination [Seite 662] in Extended Warehouse Management (EWM).

Integration Route determination is integrated with the following components and systems: Task

System

Perform the Global ATP check and backorder processing

SAP Advanced Planning and Optimization (SAP APO)

Create sales orders and perform the Global ATP check

SAP CRM and SAP APO

Perform the Global ATP check when converting unchecked deliveries into checked deliveries

ERP system and SAP APO

Make route-relevant changes, for example, change delivery date/time or goods recipient

Delivery processing in EWM

If you want to perform dangerous goods checks, you must ensure that route determination is integrated with the ERP component EH&S.

Environment, Health and Safety (EH&S)

The following table shows the systems that you must implement to define master data: System

Master Data

SAP CRM

Business partners

ERP system

Materials (products) and plants

SCM Basis

Locations, transportation lanes, calendars, means of transport, and general transportation cost profile

Prerequisites ●

You have defined the following in the master data for transportation (route determination): ○

Locations

○

Transportation lanes

○

Zones [Seite 646]

○

Routes [Seite 641]

○

Carrier profile for routing guide [Seite 647]

○

General transportation cost profile [Seite 649]

SAP Extended Warehouse Management (SAP EWM)

510

638

SAP Online Help

20.07.2007

●

You have defined the means of transport and, if necessary, hierarchical relationships between means of transport [Seite 651] in the SCM Basis master data.

●

You have defined a transportation zone hierarchy in Customizing for SCM Basis. For more information, see the Implementation Guide (IMG) under Routing Guide → Define Transportation Zone Hierarchy.

●

If you want to perform route determination within a cross-docking context, you must define cross-docking routes [Seite 644]. For more information, see Route Determination as Part of Cross-Docking [Seite 655].

●

The routing guide is only called if the system finds the scheduling schema SCHEDL_ROUTE when performing a Global ATP check for a sales order in SAP CRM or for a delivery in the ERP system. You configure this in Customizing for SAP APO under Global Available-to-Promise (Global ATP Check) →Transportation and Shipment Scheduling →Scheduling with Configurable Process Scheduling → Assign Schema and Activity to a Condition Type List. If you have defined your own scheduling procedures and they use the routing guide, you have to assign them.

●

To enable the integration of route determination with the components and systems listed above, you must activate the Activate RG indicator in Customizing for SCM Basis under Routing Guide → General Settings for Route Determination.

●

If you want the master data in various systems to always have the same status, you must configure the distribution of master data. For more information, see Distribution of Master Data [Seite 666].

●

To perform route determination as part of delivery processing, you must execute the IMG activity Activate or Deactivate Route Determination in Customizing for EWM. For more information, see Goods Issue Process → Outbound Delivery → Route Determination.

Features Route determination comprises the following steps: ●

Static route determination [Seite 653] The system determines possible trips from the available routes. When doing this, the system can take into account the assignment of carriers to the geographical data, such as legs.

●

Scheduling [Seite 656] The system calculates the start or end dates/times for the trips found. When doing this, it takes into account calendars and times for the activities departure, transportation, arrival, and, transshipment:

●

○

Forward scheduling: the system uses a start date/time (for example, order creation date/time) to calculate the end date/time (for example, delivery date/time).

○

Backward scheduling: the system uses an end date/time (for example, requested delivery date/time) to calculate the start date/time.

Dangerous goods check [Seite 973] The system first checks if a product is classified as dangerous goods. The system then checks if the product is allowed to be transported within a series of jurisdictions [Extern], for example, countries using a certain means of transport. These two checks are performed in EH&S services [Seite 967].

SAP Extended Warehouse Management (SAP EWM)

510

639

SAP Online Help

20.07.2007

If the product is classified as being dangerous goods and is allowed to be transported with the means of transport concerned, the system checks if the assigned carriers can accept dangerous goods. It rejects all carriers that do not offer dangerous goods transportation along the legs used. ●

Calculation of transportation costs [Seite 660] The system calculates the transportation costs for all the trips found. When doing this, it takes into consideration fixed transportation costs, distance-dependent costs (based on the transportation distance), time-dependent costs (based on the transportation duration), and weight-dependent costs. It also takes into consideration penalty costs for a premature or delayed delivery and a premature or delayed pickup. The costs that you have defined are evaluated by the system in the following order: a. Costs from the carrier profile b. Costs from the general transportation cost profile or costs that you have defined for transportation lanes

You can use the Business Add-In (BAdI) /SCTM/EX_RG_COST to determine alternative values or to adjust the values determined by the routing guide. ●

Additional filtering If you want to use your own criteria to perform additional filtering on the trips that have been found up to now, you can implement the BAdI /SCTM/EX_RG_FILTER.

●

Valuation For each request, the system first considers only trips with complete cost information, in other words, trips for which you have defined costs for all the legs. If no such trips exist, the system falls back on trips with incomplete cost information. The system then sorts the trips according to the costs determined. If the system finds multiple trips with identical costs, it sorts the trips by date. In the case of forward scheduling, the system gives preference to the earliest start date. In the case of backward scheduling, it gives preference to the latest end date. In cases where route determination is performed in the background, the system returns the best result only, in other words, the trip with the lowest costs. It rejects the remaining results. When you simulate route determination, you can choose which results the system is to display: ■

Display the best results

■

Display all results In this case, the system simply sorts the trips and does not reject the less favorable results. Furthermore, it also displays the trips with incomplete cost information.

SAP Extended Warehouse Management (SAP EWM)

510

640

SAP Online Help

20.07.2007

Route Definition Sequence of legs that are connected by transshipment locations [Extern].

Use The route represents a framework or corridor that comprises a multitude of trips, in other words, possible concrete itineraries. The system uses routes to determine trips in route determination [Seite 638]. The following figure shows a route with three legs that are connected by the transshipment locations P and M. It also shows a (red) trip for the case where all stop-offs in the middle leg are optional and a (blue) trip for the case where these stop-offs are mandatory. Transshipment Location P

Destination Location Z Le g

Start Location A

Transshipment Location M

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

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

Structure Leg A leg is assigned uniquely to a route, in other words, it cannot be part of multiple routes. You define legs as a sequence of stops. Each stop is a supply chain unit (SCU) [Seite 53], in other words, a location or zone [Seite 646]. The stops that connect two consecutive legs must be locations. By specifying whether the stop-offs are optional or mandatory, you define which locations the carrier is to serve in which order. You assign exactly one means of transport to each leg. In most cases, adjacent legs of a route have different means of transport. However, it might also be necessary to change legs due to various properties of the legs. Nonetheless, in most cases, the legs of a route represent its unimodal parts. Stop At stop level, you can assign a mode of transport for foreign trade to each location. The system then takes into account this mode of transport for outbound shipments in the case of exports. The value that represents this mode of transport is dependent on the country in which the location lies. The system does not check if the mode of transport semantically matches the means of transport used for the leg of this location. Since, in most cases, the system cannot define a unique country for zones, it does not permit you to define a mode of transport for such stops.

SAP Extended Warehouse Management (SAP EWM)

510

641

SAP Online Help

20.07.2007

In static route determination, the system determines the mode of transport for foreign trade for outbound shipments (trips) in the following sequence: 1. Country of first location 2. Part of the location sequence of the trip that runs from the first location within this country 3. The first location in this part of the location sequence when going backward that is a stop along the leg and for which a mode of transport for foreign trade was defined, in other words, the location that lies closest to the border. Carrier Assignment You can assign as many different carriers as you want to your means of transport or any of its subordinate means of transport for the leg. You can specify whether dangerous goods can be transported for each such combination of leg, means of transport, and carrier. In static route determination, the system defines the carrier for a trip as the carrier for the first leg who can transport dangerous goods, if required, and for which you have defined the lowest costs for transportation along this leg in the carrier profile. Departure Calendar Assignment You can define a departure calendar for the leg. If the departures for a specific request type do not correspond with the departure calendar for the leg, you can also define a specific departure calendar for this request type. The system takes into account departure calendars when scheduling [Seite 656] a trip for both the start location of the request and for each transshipment location served. Validity and Restrictions You can restrict the validity of a route by specifying the following: ●

A validity period that the system compares with the cutoff time of a single request.

●

Permitted shipping conditions that the system compares with the shipping conditions of a single request.

●

Permitted request types that the system compares with the request type of a single request. You can specify permitted request types at the header level of the route and for each stop within the leg (customer, for example). The request types at stop level must be part of the request types that you specify at header level. Request types at stop level have a higher priority than those at header level. Accordingly, the request types at header level are valid for those stops for which you have not defined separate request types.

●

Permitted transportation groups that the system compares with the transportation groups of the products in a single request.

●

Weight limits for single and collective requests that the system compares with the total weight of the products in the single request or in multiple combined requests You can also specify weight limits for single and collective requests for each stop within a leg. These limits overwrite the relevant limits that you specify for the route at header level.

●

Volume limits for single and collective requests that the system compares with the total volume of the products in the single request or in multiple combined requests You can also specify volume limits for single and collective requests for each stop within a leg. These limits overwrite the relevant limits that you specify for the route at header level.

●

Dimension limits (length, width, and height)

SAP Extended Warehouse Management (SAP EWM)

510

642

SAP Online Help

20.07.2007

You can specify the maximum dimensions that a product is permitted to have to be valid for a certain route. The system compares these dimensions with those that you defined in the product master. You can also define various lead times for the different request types. These influence the start time of a trip in scheduling.

SAP Extended Warehouse Management (SAP EWM)

510

643

SAP Online Help

20.07.2007

Cross-Docking Route Definition One or more inbound routes or one or more outbound routes that are connected by exactly one cross-docking location (warehouse or distribution center relevant to cross-docking).

Use You use cross-docking routes (CD routes) to link routes to route networks. The system takes into account CD routes when you use route determination [Seite 638] as part of cross-docking [Seite 544]. Here you can define per route pair (inbound route and outbound route) whether goods at the cross-docking location (CD location) are to remain on the same vehicle or whether they are be loaded onto a different vehicle.

Structure To define a CD route, you must make the following settings: ●

You specify a CD location for the route at header level.

●

You specify one or more inbound routes on the CD Routes tab page. Here the destination location of all these routes must be identical with the CD location.

●

You specify one or more outbound routes on the CD Routes tab page. Here the start location of all these routes must be identical with the CD location. By specifying a different CD route as the inbound or outbound route, you can create a route network with multiple CD locations. Here an outbound CD route from CD location 1 must have at least one inbound route with the start location CD location 1. An inbound CD route to CD location 2 must have at least one outbound route with the destination location CD location 2.

●

On the CD Attributes tab page, you define the required attributes, for example, whether transshipment is not required (goods remain on the same vehicle), for the route pairs that consist of inbound and outbound routes.

You define CD routes in the master data for Extended Warehouse Management (EWM) under Master Data → Shipping and Receiving → Route Determination → Maintain Route.

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

SAP Extended Warehouse Management (SAP EWM)

510

644

SAP Online Help

20.07.2007

Cross-Docking Route 2 CrossDocking Location 2

Rou (Inb te 1 oun d)

ute Ro

3 ute Ro

2

CrossDocking Location 1

e6 Rout

Rou te 5

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

645

SAP Online Help

20.07.2007

Zone Definition A zone comprises a number of locations. You can define the following types of zone: ●

Direct zone You define a direct zone by directly assigning locations to this zone.

●

Postal code zone In the case of postal code zones, you indirectly define the locations contained in the zone. To do this, you assign a number of postal code intervals to a postal code zone. The postal code zone then contains all the locations that lie in at least one of these postal code intervals.

●

Region zone In the case of region zones, you indirectly define the locations contained in the zone. To do this, you assign countries, and optionally a number of regions, to a region zone. The region zone contains all locations that lie in one of the selected countries and in at least one of the regions, if you have assigned regions.

●

Leg zone In the case of leg zones, you indirectly define the locations contained in the zone. You define a leg of a route as a sequence of locations and, optionally, zones (direct zones, region zones, or postal code zones). The leg zone then contains all the locations that are either part of this sequence or that belong to a zone that is part of this sequence.

In the zone definition, the system does not display the zones assigned to a leg, but instead simply the locations contained in the zones. ●

Mixed zone You define mixed zones from locations, postal code intervals, and regions.

Use The properties assigned to a zone can be partly transferred to all its locations. In this way, the zone helps to reduce the volume of master data.

All the locations that are supplied by the same warehouse are grouped in a zone. The main advantage of postal code zones, region zones, and leg zones is that you can take into account one-off locations. One-off locations are locations that are not created as master data in the system. You can therefore map unloading locations, for example, that are important for one request only. One-off locations are described by addresses where you must specify at least a country, a region, and a postal code. The country makes the postal code and region information unique. You define and maintain direct zones, postal code zones, and region zones in the definition of zones for routes in the master data for transportation (route determination). You define and maintain leg zones in the definition of routes in the master data for transportation (route determination). You can only display them in the definition of zones.

SAP Extended Warehouse Management (SAP EWM)

510

646

SAP Online Help

20.07.2007

Carrier Profile for the Routing Guide Definition Profile in which you define data for the carrier (business partner with the role Carrier).

Use The system takes into account the carrier profile data when determining routes [Seite 638] in the routing guide. You can create only one profile for each carrier. You define the carrier profile for the routing guide in the master data for transportation (route determination).

Structure Header Data The carrier profile for the routing guide contains the following header data: ●

Carrier address

●

Communication data

●

Administrative data

Geographical Data and Means of Transport You can assign geographical data (locations or zones) and means of transport to the carrier. During route determination, the system only takes into account the assignment of a leg zone and a means of transport that is either the same as the means of transport for the leg or superior to it. For more information, see Hierarchical Relationships Between Means of Transport [Seite 651]. You can also specify whether the carrier for this assignment can accept dangerous goods. Transportation Groups and Product Freight Groups The system considers a carrier's transportation groups and product freight groups as restrictions (whether the carrier can accept the products in a request) when determining routes in the routing guide. Freight Code Sets Freight code sets are used in Transportation Management in Extended Warehouse Management (EWM) to define freight codes. You use freight codes to communicate with freight forwarders and other service providers. Transportation Costs During route determination, the system takes into account the transportation costs with a higher priority than the costs in the general transportation cost profile [Seite 649]. ○

Global transportation costs Global transportation costs are fixed transportation costs that you define for a carrier’s means of transport.

○

Dimension-dependent transportation costs You define dimension-dependent transportation costs for a carrier’s means of transport in a certain dimension and relevant unit. The following dimensions are supported:

SAP Extended Warehouse Management (SAP EWM)

510

647

SAP Online Help

20.07.2007 ●

Distance

●

Duration (transportation duration)

●

Quantity (weight)

●

Stop-offs (The system does not currently evaluate them.)

You define dimension-dependent costs of 20.00 per kilometer driven for the dimension Distance.

SAP Extended Warehouse Management (SAP EWM)

510

648

SAP Online Help

20.07.2007

General Transportation Cost Profile Definition Profile that contains costs for transportation planning.

Use If you specify a general transportation cost profile in Customizing for SCM Basis under Routing Guide → General Settings for Route Determination, the system takes into account the relevant costs during static route determination [Seite 653].

The costs that you define in the general transportation cost profile are not actual costs, but instead they represent a theoretical value.

Structure You define the following costs in the general transportation cost profile: ●

Location-specific costs You can define the following penalty costs for each priority: ○

Earliness costs (per day) for pickup or delivery

○

Lateness costs (per day) for pickup or delivery

A trip that has been determined by static route determination only has a premature pickup or delivery, if the request contains a start date/time or an end date/time and the pick-up or delivery date/time that has been determined lies before this requested date/time. Correspondingly, a trip only has a delayed pickup or delivery, if the request contains a start date/time or an end date/time and the pick-up or delivery date/time that has been determined lies after this requested date/time. ●

Transportation-specific costs These are fixed transportation costs that are incurred once for each means of transport used in the route determination run. They are independent of the actual transportation (in other words, distance, and so on).

●

Dimension-specific costs These are variable transportation costs per unit for the following dimensions: ○

Time

○

Distance

○

Transported quantity per distance

These costs refer to the consumption of the dimensions of a vehicle for a request. ●

Transportation-lane-specific costs These are variable transportation costs per unit and means of transport. The values that are displayed on this tab page, for example, locations or zones as the start location or destination location, as well as means of transport costs come from the transportation lane.

SAP Extended Warehouse Management (SAP EWM)

510

649

SAP Online Help

20.07.2007

To define general transportation cost profiles, on the SAP Easy Access screen, choose SCM Basis → Routing Guide → General Transportation Cost Profile.

SAP Extended Warehouse Management (SAP EWM)

510

650

SAP Online Help

20.07.2007

Hierarchical Relationships Between Means of Transport Use Route determination takes into account hierarchical relationships between means of transport when determining certain attributes. If the system does not find a certain attribute for a means of transport because you have not defined it, it automatically tries to find the attribute for the means of transport directly superior to the first one. If it does not find the attribute there either, the system tries to find it for the means of transport that is directly superior to this one, and so on. By defining hierarchical relationships between your means of transport, you can reduce the effort required to enter your attributes. If, for example, you want to use route determination quickly without having to define a large number of attributes, it is sufficient to define the required attributes for the highest means of transport in the hierarchy only. The system then takes these attributes into account for all subordinate means of transport. If you subsequently define attributes for individual subordinate means of transport bit by bit, the system then takes these into account. Defining hierarchical relationships is optional.

Integration To take into account superordinate means of transport, integration with SAP Advanced Planning and Optimization (SAP APO) is required.

Prerequisites You have defined means of transport and have specified superordinate means of transport for each of them in Customizing for SCM Basis under Master Data → Transportation Lane → Maintain Means of Transport. In this way, you have defined hierarchical relationships between your means of transport.

Features Route determination takes into account hierarchical relationships for the following attributes: ●

Attributes that you have defined when defining the means of transport, for example, average speed for scheduling

●

Attributes that you have defined when defining transportation lanes for the means of transport, for example, transportation costs, transportation duration, and transportation distance

●

Carriers that you have assigned to the means of transport when defining legs You can assign a carrier not only to the means of transport for a leg but also to each means of transport superordinate to it. This is advantageous if you change the means of transport for the leg by entering a superordinate means of transport after you have assigned the carrier. In this case, the system automatically deletes all carrier assignments that do not refer to the new means of transport for the leg or one of its superordinate means of transport.

You have specified means of transport TRUCK_LARGE for leg 1. You have specified CR 1 as the carrier for TRUCK_LARGE and CR 2 as the carrier for TRUCK.

SAP Extended Warehouse Management (SAP EWM)

510

651

SAP Online Help

20.07.2007

If you now change the means of transport for leg 1 from TRUCK_LARGE to TRUCK, the system automatically deletes the assignment of CR 1 to TRUCK_LARGE. ●

Costs that you have defined in the carrier profile [Seite 647] or in the general transportation cost profile [Seite 649].

If you have assigned a means of transport to a leg, route determination takes into account this exact means of transport and its superordinate means of transport only but not the subordinate means of transport. Otherwise, there would be too many solutions. For more information about taking into account hierarchical relationships in route determination, see SAP Note 818982.

Example The following table shows the hierarchical relationships between different means of transport: Means of Transport

Average Speed

Superordinate Means of Transport

TRUCK

80 km/h

-

TRUCK_LARGE

-

TRUCK

TRUCK_SMALL

-

TRUCK

TRUCK 51’

60 km/h

TRUCK_LARGE

TRUCK 48’

-

TRUCK_LARGE

TRUCK 24’

-

TRUCK_SMALL

TRUCK 21’

-

TRUCK_SMALL

This produces the following hierarchical relationships: TRUCK TRUCK_SMALL TRUCK 21’

TRUCK 24’

TRUCK_LARGE TRUCK 48’

TRUCK 51’

When you enter the means of transport TRUCK_LARGE, the system determines an average speed of 80 km/h. Since you have not defined a value for means of transport TRUCK_LARGE, the system takes the value for the superordinate means of transport TRUCK. When you enter the means of transport TRUCK 51’, the system determines an average speed of 60 km/h, in other words, the value that you have defined for the means of transport TRUCK 51’. When you enter the means of transport TRUCK 24’, the system determines an average speed of 80 km/h. Since you have not defined a value for either means of transport TRUCK 24’ or means of transport TRUCK_SMALL, the system takes the value for the superordinate means of transport TRUCK.

SAP Extended Warehouse Management (SAP EWM)

510

652

SAP Online Help

20.07.2007

Static Route Determination Use Static route determination is part of route determination [Seite 638] in the routing guide. In static route determination, the system uses the existing routes to determine possible trips, in other words, instances of these routes [Seite 641].

Prerequisites See the prerequisites under Route Determination [Seite 638].

Features Determination of Geographically Possible Routes The system first determines the number of routes that are geographically possible. Here the route must contain the start location and destination location from the request in the correct order. A leg of a route and therefore the route itself contains a location if at least one stop [Extern] in its sequence of stops contains this location. A stop of a leg contains a given location if one of the following conditions is met: ●

The stop is a location and is identical to the given location.

●

The stop is a direct zone [Seite 646] and includes the given location.

●

The stop is a postal code zone or a regional zone and includes the postal code or the region of the given location.

A route contains the start location and destination location from the request in the correct order in one of the following cases: ●

At least one leg that contains the start location lies before another leg that contains the destination location in the leg sequence of the route.

●

A leg in this route contains both the start location and the destination location, and at least one stop that contains the start location lies before another stop that contains the destination location in the stop sequence of this leg.

Determination of Valid Routes A route that is possible from a geographical point of view is valid for a request if it meets all the following conditions: ●

You have not explicitly excluded this route.

●

You have not marked the route for deletion.

●

You have not defined any restrictions for this route that make it invalid for the request (see Route [Seite 641]).

Creating the Location Sequence of a Trip In accordance with the division of a route into legs, the location sequence of a trip is also divided into legs. For each relevant leg of a valid route, the system uses the stop sequence to form a fixed sequence of locations for the relevant leg of the trip. A leg of a route is only relevant to a request in the following cases:

SAP Extended Warehouse Management (SAP EWM)

510

653

SAP Online Help

20.07.2007

●

It is the start leg for the request because it is the closest of all the legs containing the start location in the request to the destination location.

●

It is the destination leg for the request because it is the closest of all the legs containing the destination location in the request to the start location.

●

It is a leg between the start leg and the destination leg of the request.

Only the following locations are relevant to the system for the location sequence of the trip: ●

Start location of the request; the last stop of the start leg that contains it is called the start stop.

●

Destination location of the request; the first stop of the destination leg that contains it is called the destination stop.

●

Each transshipment location that connects two consecutive relevant legs

●

Each location in a relevant leg that you have marked as mandatory As a result, the zones that you have defined as (optional) stops along legs are skipped when the location sequence of the trip is created.

To create the location sequence of the trip, the system arranges the relevant locations in accordance with the following rules: ●

Two locations of different legs Their arrangement is given by the leg sequence of the route.

●

Two locations of different stops along the same leg Their arrangement is given by the stop sequence of the leg.

●

Two locations of the same stop (along the same leg) This case only occurs if both the start location and the destination location from the request lie in the same zone and you have defined this zone as a stop along a leg. In this case, the location sequence of each trip consists of the start location and the destination location only.

Assignments Among other reasons, a geographical route is not valid for a request if you have excluded the means of transport of a relevant leg as a result of the request. On the other hand, you reduce the assignment to its means of transport by explicitly excluding carriers.

SAP Extended Warehouse Management (SAP EWM)

510

654

SAP Online Help

20.07.2007

Route Determination as Part of Cross-Docking Use When you use route determination [Seite 638] as part of cross-docking [Seite 544], the system takes into account cross-docking routes (CD routes) [Seite 644].

Prerequisites ●

You have defined request types for CD routes in Customizing for SCM Basis under Routing Guide → Route Determination → Define Request Types for Routing Guide.

●

You have defined CD routes. Here you have made sure that all the routes involved are suitable for cross-docking, in other words, they have one of the request types defined previously.

Features The system first searches for possible route sequences in the route network that meet the following conditions: ●

The start location of the request is contained in the first route of the route sequence.

●

The destination location of the request is contained in the last route of the route sequence.

Then it checks each possible route sequence to ascertain whether the attributes of the individual routes agree with the requirements in the request, for example, shipping conditions, weight restrictions, and request type. If a route in a route sequence does not meet these requirements, the system rejects the entire route sequence. The result is a number of route sequences that the system represents as a trip, in other words, a sequence of legs. The difference in comparison with route determination without cross-docking is that the trip covers multiple routes in this case. The additional steps in route determination take place in the same way as in the case of route determination without cross-docking (see Route Determination [Seite 638]).

You can use the Business Add-In (BAdI) Enhancements for Scheduling in Routing Guide (/SCTM/EX_RG_PROCESS_SCHED) to determine alternative durations for the transshipment activities.

SAP Extended Warehouse Management (SAP EWM)

510

655

SAP Online Help

20.07.2007

Scheduling Use In scheduling, the system calculates start and end dates/times for all valid trips. Here it takes into account calendars and times for the following activities: ●

Transshipment

●

Departure/shipping

●

Transportation

●

Arrival/receipt

Scheduling is part of route determination [Seite 638] in the routing guide. When you simulate route determination [Seite 662], the system displays detailed results of scheduling. The following sections are particularly relevant to this case.

Integration See Route Determination [Seite 638].

Prerequisites ●

You have defined the following in the master data for route determination: ○

Locations with geocoordinates

○

Transshipment locations with minimum goods wait time [Extern] and arrival calendar

○

Optionally, transportation lanes with transportation calendars, transportation durations, and distances

○

Routes [Seite 641] with departure calendars

To do this, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Shipping and Receiving → Route Determination. ●

You have defined the average speed and the “actual distance versus aerial distance” factor for all relevant means of transport in Customizing for SCM Basis under Master Data → Transportation Lane → Maintain Means of Transport.

●

See also the prerequisites under Route Determination [Seite 638].

Features Scheduling is based on the following activities: ●

Transshipment

●

Departure/shipping

●

Transportation

● Arrival/receipt The system takes into account these activities in this order for each leg of trip, whereby transshipment is not relevant to the first leg of the trip. The routing guide chooses the relevant locations of the leg before scheduling, and defines a fixed order for them in accordance with the sequence strategy that you have defined for the leg. Here the following applies:

SAP Extended Warehouse Management (SAP EWM)

510

656

SAP Online Help

20.07.2007

●

A location is part of a leg if either itself or one of its zones is a stop along the leg.

●

A location of a leg is relevant if it does not lie before the start location or after the destination location of the request, and is either a transshipment location or part of a leg for which you cannot skip stops.

In scheduling, the routing guide only takes into account transportation lanes between sequential locations in the sequence that the routing guide defined before scheduling. Scheduling of activities is based on the following data: ●

Transshipment ○

●

Departure/shipping ○

●

●

Transshipment duration: minimum duration of the goods wait time at the transshipment location

Departure calendar: departure calendar of the leg, if available, or shipping calendar of the start or transshipment location

Transportation (for each stage of a trip) ○

Transportation calendar: you define the transportation calendar for a stage by defining a transportation lane.

○

Transportation duration: if you have not defined a transportation duration for the transportation lane, the system checks if a value exists for the transportation distance for the transportation lane. It then multiplies this with the average speed of the means of transport used for the leg. If you have not defined any of these values for the transportation lane or have not defined a transportation lane at all, the system estimates the transportation distance on the basis of the geocoordinates of the two locations. It then multiplies this value with the average speed of the means of transport used for the leg.

Arrival/receipt ○

Arrival calendar: Receiving calendar of the transshipment or destination location

For the results of scheduling, see here [Seite 658].

Activities To simulate route determination, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Transportation → Route Determination → Simulate Route Determination.

SAP Extended Warehouse Management (SAP EWM)

510

657

SAP Online Help

20.07.2007

Results of Scheduling Use The results of scheduling that you aim for in route determination are defined as listed in the following tables. Here the following applies: ●

If route determination is executed automatically in the background, the system only displays the departure and arrival of the trip at header level.

●

When you simulate route determination, the system displays all the dates/times and durations listed below.

Results at header level (that is, for the entire trip) Forward Scheduling Date/Time

Comment

Trip cutoff time (date/time)

The scheduling start is the current time, unless you have specified a different value when simulating route determination. The system then calculates the cutoff time of the trip from the scheduling start and the cutoff time of the route by using the later of the two dates/times. The cutoff time of the route is calculated from the order creation time plus the lead time that you have defined for the route on the basis of the request type. The order creation time is the current time, unless you have specified a different value when simulating route determination.

Trip departure (date/time)

The departure of the trip is calculated from the cutoff time of the trip, taking into account the departure calendar of the start location. (This is the departure calendar for the relevant leg dependent on the request type, or the shipping calendar of the location.)

Trip arrival (date/time)

The arrival of the trip is calculated from the departure of the trip plus the transportation duration of the trip, taking into account the arrival calendar of the destination location (receiving calendar of the location). The transportation duration of the trip is the total of all transportation and transshipment durations for all legs in the trip.

Backward Scheduling Date/Time

Comment

Trip arrival (date/time)

The arrival of the trip is calculated from the end that you specified during the simulation of route determination, taking into account the arrival calendar of the destination location.

SAP Extended Warehouse Management (SAP EWM)

510

658

SAP Online Help

Trip departure (date/time)

20.07.2007

The departure of the trip is calculated from the arrival of the trip minus the transportation duration of the trip, taking into account the departure calendar of the start location. If the time calculated is before the cutoff time, the system puts the time back into the past by the relevant lead time.

Results at item level (that is, for the individual legs of the trip) Date/Time

Comment

Transportation duration for the leg

The transportation duration of the leg is calculated from the total of the transportation durations between the relevant locations, taking into account the relevant transportation calendar. In the case of transportation durations, they can be estimates.

Transshipment duration for the leg

The transshipment duration of the leg is the period of time of the transshipment, taking into account the minimum goods wait time.

Forward Scheduling Date/Time

Comment

Leg departure (date/time)

In the case of the first leg, the departure of the leg is the same as the trip departure. For each additional leg, it is calculated from the transshipment end, taking into account the departure calendar of the transshipment location.

Leg arrival (date/time)

The arrival of the leg is the same as the departure of the leg plus the transportation duration of the leg, taking into account the arrival calendar of the transshipment location or destination location.

Backward Scheduling Date/Time

Comment

Leg arrival (date/time)

For the last leg of the trip (first leg for scheduling), the arrival of the leg is the same as the trip arrival. For each additional leg, it is the transshipment start, taking into account the arrival calendar of the transshipment location.

Leg departure (date/time)

The departure of the leg is the same as the arrival of the leg minus the transportation duration of the leg, taking into account the departure calendar of the start location or transshipment location.

See also: Simulation of Route Determination [Seite 662]

SAP Extended Warehouse Management (SAP EWM)

510

659

SAP Online Help

20.07.2007

Calculation of Transportation Costs Use During route determination [Seite 638], the system calculates the transportation costs for each of the trips that are determined.

Features The system first adds up the following costs to produce a total cost value: ●

●

●

The penalty costs for premature or delayed delivery, or for premature or delayed pickup for each trip, dependent on the following values: ○

Period of time of the earliness or delay

○

Priority of the location where the earliness or delay occurred

The fixed transportation costs for each leg of a trip, dependent on the following values: ○

Carrier for the leg (if you have assigned one)

○

Means of transport for the leg

The following costs for two consecutive locations along a leg: ○

○

○

Distance-dependent costs, dependent on the following values: ■

Carrier for the leg (if you have assigned one)

■

Means of transport for the leg

■

Transportation distance between the two locations

Time-dependent costs ■

Carrier for the leg (if you have assigned one)

■

Means of transport for the leg

■

Transportation duration between the two locations

Weight-dependent costs ■

Carrier for the leg (if you have assigned one)

■

Means of transport for the leg

■

Total weight of the products transported between the two locations

■

Transportation distance between the two locations

The system requires a cost value or cost factor to calculate these costs. You define the cost value or cost factor in one of the following places: ●

In the carrier profile

●

In the general transportation cost profile

●

In the relevant transportation lane

SAP Extended Warehouse Management (SAP EWM)

510

660

SAP Online Help

20.07.2007

The system searches for a cost value or cost factor in these three places in the sequence specified. As soon as it finds an entry, it terminates the search and performs the cost calculation. When calculating transportation costs, the system takes into account hierarchical relationships between means of transport [Seite 651].

During route determination, the system has determined a trip with one leg with means of transport M and carrier F. If you have not defined a cost factor for the means of transport M in the transportation cost profile for carrier F but have defined a cost factor for a means of transport superior to M, the system also takes into account this cost factor for M.

You can use the Business Add-In (BAdI) Cost Determination in Route Determination (/SCTM/EX_RG_COST) to determine alternative values or to adjust the values found by the routing guide.

SAP Extended Warehouse Management (SAP EWM)

510

661

SAP Online Help

20.07.2007

Simulation of Route Determination Use You can use this report to manually simulate route determination in the routing guide. As a basis for the simulation, you choose a strategy and parameter values. All the output tables for the routing guide such as trips, legs, and dangerous goods information are displayed as the result.

Prerequisites See Route Determination [Seite 638].

Features Selection Strategies When you choose the Route Information strategy, the system simply determines a trip for your location data. In the case of the other strategies, the system also performs scheduling, a dangerous goods check, a cost calculation and, on the basis of the strategy chosen, it selects and arranges the trips determined. Request data To simulate route determination, you specify the start location and the destination location. If you have already defined a location with an address, you only have to specify the location name. Otherwise, you specify the location using your address data. Furthermore, specify a shipment direction (selection parameter). You use the shipment direction to specify if it is an outbound delivery process or an inbound delivery process. Selection parameters If the strategy you have chosen includes scheduling [Seite 656], you have specified the following: ●

Start date/start time if you have chosen forward scheduling

●

End date/end time if you have chosen backward scheduling

If in the route definition you have defined the lead time of the routes depending on the request types, you can take into account the lock time. To do this, specify the request type and the request date/time if this differs from the current date/time. For more information about scheduling, see Results of Scheduling [Seite 658]. You optionally enter the following for calculating penalty costs for premature or delayed pickup or delivery: ●

Start date/start time if you have chosen backward scheduling

●

End date/end time if you have chosen forward scheduling

Restrictions The following table shows how to influence the determination of trips:

Route

Specify Value

Exclude Value

The system only returns a trip if it is based on this route.

The system only returns a trip if it is based on a different route.

SAP Extended Warehouse Management (SAP EWM)

510

662

SAP Online Help

20.07.2007

Shipping condition

The system only returns a trip if you have defined this shipping condition for the underlying route (see Route [Seite 641]).

Not possible

Means of transport

The system only returns a trip if you have assigned this means of transport to the leg whose destination location is the customer (outbound delivery process) or whose start location is the supplier (inbound delivery process).

The system only returns a trip if you have not assigned this means of transport to the leg whose destination location is the customer (outbound delivery process) or whose start location is the supplier (inbound delivery process).

Carrier

The system only returns a trip if you have assigned this carrier to the leg whose destination location is the customer (outbound delivery process) or whose start location is the supplier (inbound delivery process).

The system only returns a trip if you have not assigned this carrier to the leg whose destination location is the customer (outbound delivery process) or whose start location is the supplier (inbound delivery process).

Products The system takes into account your input about the products to be transported in the following way: ●

If your chosen strategy includes a dangerous goods check, the system only displays a trip as the result if the geographical course of the trip agrees with the dangerous goods relevance of the products.

●

If you have defined a weight interval for the single request for a route, the system only returns a trip based on this route if the total weight of the request based on the product master lies in this interval.

●

If you have defined a volume interval for the single request for a route, the system only returns a trip based on this route if the total volume of the request that is based on the product master lies in this interval.

●

If you have defined maximum vales for length, width, and height for the route, the system only displays a trip based on this route as the result of route determination if the values for length, width, and height defined in the product master do not exceed these maximum values.

Control parameters You can use the following control parameters to influence the output of system messages in the results area Log: ●

Max. problem class for messages The system only displays messages that are assigned either to the problem class you have chosen or to a higher one (filter).

If you activate buffering, the system can minimize the response times for multiple requests. As a prerequisite, you must not leave the transaction in between requests.

Result Results: Trip (Header Level)

SAP Extended Warehouse Management (SAP EWM)

510

663

SAP Online Help

20.07.2007

Results

Comment

Rank

The system arranges the trips in accordance with the total costs calculated, whereby the completeness of the costs is the sort criterion.

Route

The system specifies the underlying route of the trip that is determined. Within crossdocking, this is the cross-docking route [Seite 644] that comprises the entire trip.

Next cross-docking location

Within cross-docking, the system displays the first location where transshipment is to occur according to the cross-docking route definition.

Costs

The total costs consist of transportation costs and penalty costs. Transportation costs include fixed costs as well as variable costs that are dependent on distance, duration, and/or weight. Both types of cost can be dependent on the choice of means of transport and carrier. Penalty costs include costs for premature delivery, premature pickup, delayed delivery, and delayed pickup.

Times for lock time, departure, and arrival of the trip

See Scheduling [Seite 656]

GTS geography group

The system specifies the GTS geography group of the route upon which the trip that is determined is based.

Results: Legs of a Trip (Item Level) Results

Comment

Leg number

The system arranges the legs of a trip in the shipment direction.

Route

Within cross-docking, the system specifies the route of the leg on which the leg of the trip is based.

Start location, destination location, and stops

The value in the Start Location of Leg field is the start location of the request or the loading location of a subsequent leg. The value in the Destination Location of Leg field is the destination location of the request or the unloading location of a previous leg. Along with the start location and destination location of the leg, the stops also include a list of locations served along the leg that you have selected.

Means of transport, carrier, and assignments

The system specifies the means of transport and, optionally, a carrier for the leg of the route upon which the leg in the trip that has been determined is based. If more than one carrier is assigned to this means of transport for the leg, the system displays the relevant combinations as assignments of the leg that you have selected (see Route [Seite 641]).

SAP Extended Warehouse Management (SAP EWM)

510

664

SAP Online Help

20.07.2007

Costs

The total costs or the penalty costs for the trip are the sum of the total costs or penalty costs for all legs in the trip.

Times for departure and arrival

See Scheduling [Seite 656]

Durations for transshipment and transportation

See Scheduling [Seite 656]

Additional Results Results

Comment

Dangerous goods information

The system specifies the result of the dangerous goods check for the products that you have specified.

Transit information

The system specifies the regions that the transportation covers for the legs of the trips that have been determined.

Log

While taking into account the control parameters that you have chosen, the system specifies the messages that have been collected over time.

Activities To start the report, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Shipping and Receiving → Route Determination → Simulate Route Determination.

SAP Extended Warehouse Management (SAP EWM)

510

665

SAP Online Help

20.07.2007

Distribution of Master Data Use If you want to perform route determination in a distributed system landscape with multiple SCM systems (SAP Supply Chain Management (SAP SCM)), you must ensure that all these systems have the same master data. Otherwise, you might get different results when you call route determination from the different systems. This is particularly important if your planning system (SAP Advanced Planning and Optimization (SAP APO)) and your execution system (Extended Warehouse Management (EWM)) lie in different SCM systems. As part of route determination, you need to distribute master data in the following cases: ●

Route determination is called in SAP Customer Relationship Management (SAP CRM) during the SAP APO availability check for sales orders.

●

Route determination is called from an ERP system during the conversion of unchecked deliveries to checked deliveries. Here the call occurs via the relevant SAP APO system too.

●

Route determination is called from various EWM systems for outbound delivery orders.

Prerequisites ●

You have set the Realtime Distrib. indicator in Customizing for SCM Basis under Routing Guide → General Settings for Route Determination. In this case, the master data is distributed automatically when you change or create it in your master system.

●

You have created and transferred a distribution model. The following steps are necessary to do this: a. Create a distribution model in the master system. To do this, call transaction BD64. Enter the following BAPIs: ■

Route->SaveReplicaMulti

■

TSPProfile->TSPProfileSavereplica

■

TransportCostProfil->TransportCostsSaveReplica

■

Zone->SavereplicaMulti

b. In the model view, generate the partner profiles that you have created. To do so, choose Environment → Generate Partner Profiles in the distribution model. c. Transfer the distribution model from the master system to the other systems. To do so, choose Edit → Model View → Distribute in the distribution model.

Activities Distribution can occur automatically or you can trigger it manually. If you want to trigger the distribution manually, choose the appropriate menu option in the following transactions: ●

Maintain Route

●

Maintain Zones for Routes

●

Carrier Profile for the Routing Guide

Alternatively, you can call the distribution program using transaction /SCTM/RG_MD_DISTRI.

SAP Extended Warehouse Management (SAP EWM)

510

666

SAP Online Help

20.07.2007

Physical Inventory Use You can use the physical inventory functions in Extended Warehouse Management (EWM) to carry out a physical inventory of products and handling units (HUs) for stock control and balance sheet purposes. You have the following options: ●

Storage-bin-specific physical inventory The document refers to a storage bin and therefore to all the products and HUs in this storage bin.

●

Product-specific physical inventory The document refers to a specific product in one or more storage bins and/or HUs.

To perform a physical inventory, you can choose between various business inventory procedures: ●

Periodic physical inventory procedure [Seite 669]

●

Continuous physical inventory procedure [Seite 670]

●

Cycle counting [Seite 673]

Integration To enable you to post differences, integration with the ERP system is necessary.

Prerequisites ●

You have defined the physical inventory areas in Customizing for SCM Basis. Furthermore, you have made the settings for the low-stock physical inventory or zerostock physical inventory and the putaway physical inventory, as required. For more information, see the Implementation Guide (IMG) under SCM Basis → Physical Inventory → Basic Settings → Define Physical Inventory Area.

●

You have made the required settings in Customizing for EWM. If you want to use cycle counting, for example, you have set the Cycle Counting indicator under Configure Cycle Counting. For more information, see the IMG under Extended Warehouse Management → Internal Warehouse Processes → Physical Inventory.

Features You can carry out a physical inventory for the following stock types: ●

Unrestricted-use stock in putaway

●

Unrestricted-use stock in the warehouse

●

Blocked stock in putaway

●

Blocked stock in warehouse

●

Quality inspection stock in putaway

●

Quality inspection stock in the warehouse

You can take inventory of all stock types in a single operation. For the products to be inventoried, one item is created in the physical inventory document for each stock type. SAP Extended Warehouse Management (SAP EWM)

510

667

SAP Online Help

20.07.2007

We recommend that you lock the relevant storage bins during the physical inventory. This is not necessary in the radio frequency (RF) environment.

Activities ...

1. You create physical inventory documents. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Physical Inventory → Create Physical Inventory Document.

In this transaction, you can create active physical inventory documents immediately. Alternatively, you can first create the physical inventory documents in this transaction, and then activate them in a separate step. For more information, see Processing of Physical Inventory Documents [Seite 674]. 2. You print out physical inventory count documents [Extern] for your physical inventory documents. To do so, you have the following options: ○

From the warehouse management monitor (Physical Inventory Documents node)

○

From physical inventory document processing To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Physical Inventory → Process Physical Inventory Document. For more information, see Processing of Physical Inventory Documents [Seite 674].

○

In the background using the report Print Physical Inventory Count Document (see Reports in Physical Inventory [Seite 682])

3. You perform a count and then enter the count results in the system. If required, you perform a physical inventory recount. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Physical Inventory → Process Physical Inventory Document. For more information, see Processing of Physical Inventory Documents [Seite 674] and Physical Inventory Using Radio Frequency [Seite 808]. 4. You post the physical inventory documents in EWM. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Physical Inventory → Process Physical Inventory Document. For more information, see Processing of Physical Inventory Documents [Seite 674]. 5. If differences exist, you can analyze them. You can then use the Difference Analyzer [Seite 677] to post the differences to the ERP system.

SAP Extended Warehouse Management (SAP EWM)

510

668

SAP Online Help

20.07.2007

Periodic Physical Inventory Procedure Use As the periodic physical inventory procedure, Extended Warehouse Management (EWM) supports an annual physical inventory (storage-bin-specific and product-specific). In an annual physical inventory, you record all stocks on a certain day or within a fairly short period (in most cases at the end of the fiscal year). During this time, you can prohibit stock movements. Furthermore, you use this procedure to carry out the physical inventory for storage bins and quants that are actually subject to continuous inventory-taking but for which no stock movements have occurred during the current fiscal year. The product-specific annual physical inventory corresponds to the storage-bin-specific annual physical inventory except that you carry it out for products.

SAP Extended Warehouse Management (SAP EWM)

510

669

SAP Online Help

20.07.2007

Continuous Physical Inventory Procedures Use In the following, the continuous physical inventory procedures supported by Extended Warehouse Management (EWM) are described in more detail. For all these physical inventory procedures, you must archive the warehouse tasks (WTs) in accordance with legal provisions. This is necessary to be able to provide proof of all individual movements involving storage bins or products over the entire fiscal year.

Ad Hoc Physical Inventory (Storage-Bin-Specific and Product-Specific) For the storage-bin-specific ad hoc physical inventory, you carry out the inventory-taking for certain storage bins at any time during the fiscal year. This physical inventory procedure is manually controlled. An ad hoc physical inventory may become necessary because a product has been damaged, for example. The product-specific ad hoc physical inventory corresponds to the storage-bin-specific ad hoc inventory except that you perform it for products. For example, you may have to make a targeted check of the stock of a certain product after receiving a complaint about the product from a customer.

Low Stock Check (Storage-Bin-Specific) The low stock check is a physical inventory procedure that you perform when confirming WTs. Here you assume that a storage bin should only contain a small quantity of a product after a stock removal in accordance with the storage bin data in EWM. You define this quantity in the form of a limit value that is based on the operative unit of measure for the product per storage type. During the physical removal of stock from storage, you check whether the storage bin data reflects the actual stock situation. Since the stock comprises only a small quantity of the product (approx. 3-5 pieces), the picker can establish the stock level at a glance, without having to carry out an explicit count. You confirm on the printed WT that you have performed the physical inventory. When you confirm the WT in the system, the system automatically creates the physical inventory document in the background on the basis of the WT. You can use the WT number to determine the physical inventory document number.

A variant of the low stock check is the zero stock check. Here the limit value is zero. You have the following options: ●

Low stock check with physical inventory (low-stock physical inventory) The first time that the stock falls below the limit value, you carry out the low-stock physical inventory. The system creates a physical inventory document.

●

Low stock check without physical inventory We recommend this setting if you want to carry out the low stock check multiple times to improve stock security. In this case, no physical inventory document is created. You must therefore carry out a physical inventory for the bin at the end of the fiscal year to create a physical inventory document.

●

You can also combine the two options. The first time that the stock falls below the limit value, the system proceeds in the same way as for the low stock check with physical inventory (low-stock physical inventory). In subsequent cases, it proceeds as for the low stock check without physical inventory, in other words, it no longer creates physical inventory documents.

SAP Extended Warehouse Management (SAP EWM)

510

670

SAP Online Help

20.07.2007

The following situations can occur: ●

You request the low stock check manually if you discover that a storage bin lies below the defined limit value after stock removal, but no low stock check has been planned for this storage bin.

●

The system automatically activates the low stock check as soon as you create a WT for a storage bin that should lie below the defined limit value after the stock removal.

When the WT is created, the system checks whether the following conditions have been met: ●

No open WT exists for the storage bin.

●

Negative quantities are not permitted for the relevant storage type.

●

Mixed storage is not permitted for the relevant storage type, in other words, only one quant exists.

In the radio frequency environment, the check is performed when you confirm the WT. If these conditions are met, the system requests that you enter the quantity counted when you confirm the WT. The following situations can occur: ●

The storage bin should be empty and really is empty (zero stock check) or the quantity in the storage bin lies below the permitted limit value (low stock check). In this case, you enter zero or the remaining quantity as the quantity counted. The system creates a physical inventory document.

●

The storage bin should be empty, but is not empty (zero stock check) or the quantity in the storage bin does not lie below the permitted limit value (low stock check). In this case, you have the following options: ○

You enter the remaining quantity. The system creates a physical inventory document and displays the differences in the Difference Analyzer [Seite 677].

○

You reject the physical inventory, for example, because the remaining quantity is too large and you cannot enter the quantity based on a quick glance, but would need to count each piece. In this case, the system does not create a physical inventory document and does not display the difference.

If some storage bins do not fall below the limit value as a result of stock removal within the fiscal year, we recommend that you also define a periodic physical inventory [Seite 669] for this physical inventory area in addition to the low stock check. This allows you to carry out a periodic physical inventory for the storage bins that have not been recorded at the end of the fiscal year.

Putaway Physical Inventory (Storage-Bin-Specific) As with the low stock check, the putaway inventory is a procedure for simplifying the work involved in carrying out a physical inventory. In this case, the physical inventory for a storage bin is carried out at the time of the first putaway in this bin in the fiscal year. The warehouse employee confirms during the first putaway that the stock in the warehouse matches the confirmed quantity in the WT after the putaway. During the current fiscal year, no further physical inventory is performed for this storage bin, even if a completely different quant is stored there at the end of the year, or if the bin is empty. In the case of the putaway physical inventory, the system checks when the WT is created whether the following conditions have been met:

SAP Extended Warehouse Management (SAP EWM)

510

671

SAP Online Help

20.07.2007

●

The storage bin is empty.

●

Mixed storage is not permitted for the relevant storage type, in other words, only one quant exists.

●

You are putting stock away for the first time in the physical inventory year.

In the radio frequency environment, the check is performed when you confirm the WT. If these conditions are met, the system requests that you enter the quantity counted when you confirm the WT. The following situations can occur: ●

The storage bin is really empty. This means that after the WT has been confirmed, the storage bin quantity is the same as the WT quantity. The system creates a physical inventory document for this WT quantity.

●

The storage bin is not empty, in other words, there are still products in the storage bin. In this case, you reject the putaway physical inventory. The system does not create a physical inventory document.

If putaway does not take place for all storage bins within a fiscal year, we recommend that you make additional provision for a periodic physical inventory [Seite 669] for the relevant storage type. This allows you to carry out a periodic physical inventory for the storage bins whose data has not yet been recorded at the end of the fiscal year.

Storage Bin Check The storage bin check is a procedure in which you check whether a product is actually stored in the storage bin in which it is supposed to be located. The quantity of the product in the storage bin is immaterial in this case. Thus, the storage bin check is not a physical inventory procedure in the true sense.

SAP Extended Warehouse Management (SAP EWM)

510

672

SAP Online Help

20.07.2007

Cycle Counting Use As a cycle-counting procedure, Extended Warehouse Management (EWM) supports productspecific cycle counting [Extern]. Cycle counting means that you carry out a physical inventory of your stocks at regular intervals during a fiscal year. By allocating products to different classes (for example, A, B, C, and D), you specify for those products the intervals or cycles at which you are going to carry out the physical inventory. This allows you to inventory fast-moving products [Extern] in your warehouse more frequently than slow-moving ones [Extern] for instance. In the warehouse management monitor [Seite 878], you can monitor the progress of physical inventory for cycle counting. For example, you can determine which products are still to be counted. To be able to provide proof of individual movements involving the products during the entire fiscal year, you must archive the warehouse tasks (WTs) in accordance with legal provisions.

SAP Extended Warehouse Management (SAP EWM)

510

673

SAP Online Help

20.07.2007

Processing of Physical Inventory Documents Use You can use this function to enter the count results for physical inventory documents (PI documents) and to process PI documents.

Prerequisites ●

You have created PI documents. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Physical Inventory → Create Physical Inventory Document. In most cases, you have also printed the physical inventory count documents [Extern].

●

In Customizing for SCM Basis, you can influence the fields and functions that are available for processing PI documents. For more information, see the Implementation Guide (IMG) under SCM Basis → Physical Inventory → Basic Settings → Define Physical Inventory Area.

Features The system displays the PI documents per storage bin (storage-bin-specific physical inventory) or per product (product-specific physical inventory). The following figure provides an overview of possible statuses in physical inventory processing. It also shows which actions are permitted for which statuses. Initial Status After Creation

I nt P Pri ment u Doc

Inactive

Printed

Activate - Deactivate Initial Status After Creation

Active

Deleted

New Document

Count Recount Counted

Recounted

Post

Posted

Depending on the status of the PI documents, you have the following options, for example:

Activate and Deactivate PI Documents An inactive PI document is not yet assigned to a warehouse order and therefore a resource. By activating the PI document, you trigger the relevant process in the warehouse. To be able to count and print PI documents, you must activate them first.

Enter and Change Count Results You can enter count data for PI documents such as the counter, count date, and quantity. You can also change count results that have already been entered, for example, if you have made a typing mistake.

SAP Extended Warehouse Management (SAP EWM)

510

674

SAP Online Help

20.07.2007

In the case of the storage bin check, you cannot enter quantities. You simply specify whether the product is available in the storage bin or not. If the product has a serial number requirement [Seite 571] B (Serial Number Requirement at Warehouse Number Level) or C (Serial Number Requirement in Inventory Management), you must enter serial numbers. The following table shows the hierarchical levels on which you can enter count results as well as the input help available: Hierarchy Level

Values

Storage bin

Empty Handling unit (HU)

Not available, complete, or empty Product

Enter the quantity

If you have to count wine bottles that are packed in cases, you can simply confirm that the handling unit (HU) is complete. This means that you do not have to open the cases.

A radio frequency transaction [Seite 808] is available for entering count results.

Post PI Documents To complete the physical inventory for a product or storage bin, you have to post the PI document. This is necessary for balancing the stock in EWM when differences exist. The PI document is given the status Posted and it is therefore completed. If differences exist, you must then post them in the Difference Analyzer [Seite 677] to the ERP system.

Trigger a Recount If you have doubts about a count result, you can trigger a recount. In this case, the system automatically creates a new PI document with reference to the original PI document.

Print PI Count Documents You can print PI count documents on which the counter writes the count results.

Delete PI Documents You can delete PI documents with the status Active, Inactive, and Counted.

Display Information Depending on the status of the PI document, the system displays the following information about the PI document items, for example: ●

Cumulative total of PI differences per product

●

Cumulative book inventory per product

●

Detailed PI differences

●

References of the PI document to warehouse orders or recounted PI documents

●

Change history

SAP Extended Warehouse Management (SAP EWM)

510

675

SAP Online Help

20.07.2007

Activities To process PI documents, on the SAP Easy Access screen, choose Extended Warehouse Management → Physical Inventory → Process Physical Inventory Document. This is the central transaction for physical inventory processing.

You can also use the transactions Enter Count Results and Create Phys. Inventory Count in List to enter count results.

SAP Extended Warehouse Management (SAP EWM)

510

676

SAP Online Help

20.07.2007

Difference Analysis Use You use this function to analyze differences and to post them to the ERP system. The aim of posting differences is to reconcile stocks in the ERP system, and, in particular, in financial accounting. Differences can arise in the following processes: ●

Creating physical inventory documents

●

Confirming warehouse tasks (WTs)

●

Claims from sales orders

●

Claims from stock transfers

You analyze differences in the Difference Analyzer.

Integration To be able to post differences to the ERP system, integration with the ERP system is necessary.

Prerequisites ●

You have defined priorities and reasons. For more information, see the Implementation Guide (IMG) under Extended Warehouse Management → Internal Warehouse Processes → Physical Inventory → Warehouse-Number-Specific Settings → Reason and Priority →:

●

○

Define Priorities

○

Define Reason for Physical Inventory

○

Define Reason for Differences

You have defined tolerance groups for the Difference Analyzer. For more information, see the IMG under Extended Warehouse Management → Internal Warehouse Processes → Physical Inventory → Warehouse-Number-Specific Settings → Define Tolerance Groups → Define Tolerance Group for Difference Analyzer.

●

You have assigned each of your users to one of these tolerance groups. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Settings → Physical Inventory → Assign User to Tolerance Group for Difference Analyzer.

Features In the Difference Analyzer, differences are displayed at both a cumulative and individual level. The individual differences are given a link to the document that has caused the difference. At a cumulative level, differences with the same stock key [Extern] are displayed in an aggregated way. In other words, they are displayed independently of the document and process in which they occurred. The aim of the cumulative display is to show the balance of the differences to reduce the number of postings to the ERP system (where possible, to zero), for example. The following information, for example, is displayed in the Difference Analyzer: ●

Tolerance excesses

SAP Extended Warehouse Management (SAP EWM)

510

677

SAP Online Help

20.07.2007

The system indicates if the absolute difference value of the cumulative row exceeds the threshold value from the tolerance group for a difference. ●

Customs blocked stock The system indicates if the stock for a difference is in customs blocked stock [Extern]. You can only post the difference if it balances with another difference from the customs blocked stock to make zero.

●

Serial number requirement The system indicates if a serial number requirement exists for a difference. In this case, you cannot post at cumulative level. For more information about the serial number requirement, see Serial Number [Seite 571].

●

Priority The priority of the document is displayed for each difference. At cumulative level, the highest priority is displayed.

●

Posting date The posting date specifies when you entered a difference. At cumulative level, the oldest posting date is displayed.

You have the following options, for example: ●

Lock differences If you first want to analyze a difference, for example, you can lock it to prevent another user from posting it. You can also enter a locking reason. When you release the difference again, the lock reason is kept for information purposes. When you lock a difference at detailed level, you also automatically lock the cumulative row.

●

Enter notes When you enter a note at detailed level, you automatically see at cumulative level that a note exists.

Status The Difference Analyzer uses the following statuses: ●

Red traffic light: posting is not possible.

●

Green traffic light: posting is possible.

●

Yellow traffic light: posting is possible with a warning.

At detailed level, the traffic light is green if all the following conditions are met: ●

No tolerance has been exceeded.

●

You have not locked a difference.

●

No stock is in customs blocked stock [Extern].

As soon as one or more of these conditions is no longer met, the traffic light for the relevant difference is red. At cumulative level, the traffic light is green if all the following conditions are met: ●

The balance does not exceed the tolerance.

●

You have not locked a difference.

●

The stock in customs blocked stock balances to make zero.

SAP Extended Warehouse Management (SAP EWM)

510

678

SAP Online Help ●

20.07.2007

There are no serial number requirements with the attribute C (Serial Number Requirement in Inventory Management).

You can influence this overall status with a customer-specific status (customer status). If, for example, the customer status turns yellow, the overall status also turns yellow (if it is not already red due to other conditions). You set the customer status in the Business Add-In (BAdI) Set Customer Status (/SCWM/EX_PI_SET_STATUS). If you have not implemented this BAdI, the customer status is always green.

Correct You can only correct differences that arose in the physical inventory. Moreover, you can only correct differences at detailed level.

During the physical inventory for a storage bin in which 31 pieces of a product should be found, you have only counted 30 pieces and have therefore entered 30 pieces as the quantity counted. Later on, you are informed that two pieces are missing and not just one. You correct the difference from one piece to two pieces. The system creates an additional physical inventory document with the quantity counted of 29 pieces and the book quantity of 30, and automatically posts this document. In the total, you then get the required difference of two pieces.

Post Differences to ERP System You can also post one or more cumulative differences or differences at detailed level to the ERP system. In the ERP system, a material document is created automatically that reflects the goods movement in Extended Warehouse Management (EWM) in the ERP system. You can no longer see the stock in the Difference Analyzer.

Activities To call the Difference Analyzer, on the SAP Easy Access screen, choose Extended Warehouse Management → Physical Inventory → Difference Analyzer.

When you enter a new warehouse in the Difference Analyzer, you must perform the search again to update the display. To schedule the posting of differences to the ERP system as a background job, on the SAP Easy Access screen, choose Extended Warehouse Management → Physical Inventory → Periodic Processing → Post Differences to ERP System.

SAP Extended Warehouse Management (SAP EWM)

510

679

SAP Online Help

20.07.2007

Physical Inventory Progress Use In the case of the physical inventory, you aim to have completely inventoried all storage bins and stocks by the end of the physical inventory year. You can display the status of this completeness (physical inventory progress (PI progress)) in the warehouse management monitor [Seite 878]. You can do this at the following levels: ●

Storage bin

●

Product

●

Cycle counting

Features Storage-Bin-Specific PI Progress A physical inventory area is completely inventoried when you have inventoried all the relevant storage bins. A warehouse is completely inventoried when you have completely inventoried all the relevant physical inventory areas. The PI progress refers to the number of storage bins that have been counted and the number that are still to be counted only. It does not refer to the effort required to count the individual storage bins.

You have 1000 storage bins in your warehouse. You have counted 100 of them. In this case, the PI progress is 10%. The completeness of a physical inventory area or warehouse remains intact. This means that if you have completely inventoried your warehouse in January at the beginning of the physical inventory year, it remains completely inventoried in December at the end of the physical inventory year. You document the goods movements that occur in the warehouse during this period by using warehouse tasks (WTs) [Seite 405]. The storage-bin-specific PI progress always refers to a physical inventory period such as a physical inventory year.

Product-Specific PI Progress A product is completely inventoried when you have counted all the stocks of this product per physical inventory area and party entitled to dispose. Here the completeness remains intact too. When you post the physical inventory document, the system performs a completeness check. The system checks for each physical inventory document whether this is the last open physical inventory document. If it is the last open physical inventory document, the system sets the completeness.

Product X is in physical inventory area M in the storage bins A, B, and C. ■

Physical inventory without movements If you first count A, then B, and then C, the system sets the completeness when you have counted C. If you then move stock, for example, from B to D, the completeness remains intact.

■

Physical inventory with movements

SAP Extended Warehouse Management (SAP EWM)

510

680

SAP Online Help

20.07.2007 After you have counted A and B, you move the product from A to D. If you now count C, the system realizes that the product is in B, C, and D, in other words, the physical inventory document for C is not the last open physical inventory document. For this reason, the system does not set the completeness.

To avoid goods movements during the physical inventory, we recommend that you count the entire stock per physical inventory area in a short space of time, or that you lock the stock during the physical inventory. The following example shows how goods movements affect the behavior of the completeness check.

For the product-specific PI progress, the storage-bin-specific documents are also included. However, the product-specific documents are not included in the storage-bin-specific PI progress. If, for example, you perform a storage-bin-specific PI on A in the example above, but you perform a product-specific PI on B and C, all the products are completely inventoried in the product-specific PI since A is also included. For the storage-bin-specific PI progress, the storage bins are not completely inventoried since B and C are not included. For the system to be able to determine the completeness, stock of the relevant product must be available in at least one storage bin in the warehouse. If the product is not available in a physical inventory area (zero stock), the system refrains from making a statement for this physical inventory area. If the product is available in all physical inventory areas except for this one and it has been completely inventoried, the entire warehouse is completely inventoried. The product-specific PI progress always refers to a physical inventory period such as a physical inventory year.

PI Progress for Cycle Counting The PI progress for cycle counting is the same as the product-specific PI progress with the exception that it does not refer to physical inventory periods but to the interval in which you count the product. If, for example, you have defined that you must count a product of the class A once a month, you must recount it every month to ensure that it is completely inventoried again at the end of the month. However, the first count is sufficient for legal requirements.

Activities To display the PI progress, on the SAP Easy Access screen, choose Extended Warehouse Management → Monitoring → Warehouse Management Monitor and in the warehouse management monitor, choose Phys. Inventory → PI Progress. To schedule the completeness check as a background job, on the SAP Easy Access screen, choose Extended Warehouse Management → Physical Inventory → Periodic Processing → Check Product for Complete Count. As a prerequisite, you must have set the ComplCheck (Completeness Check Online/Offline (Report)) indicator. For more information, see the Implementation Guide (IMG) under SCM Basis → Physical Inventory → Basic Settings → Define Physical Inventory Area.

SAP Extended Warehouse Management (SAP EWM)

510

681

SAP Online Help

20.07.2007

Reports in Physical Inventory The following reports are available in physical inventory for work scheduling, performing the physical inventory, and correcting errors. To call the reports, on the SAP Easy Access screen, choose Extended Warehouse Management → Physical Inventory → Periodic Processing.

Report for Work Scheduling Determine and Set Prices from ERP You can use this report to download product prices from the ERP system in Extended Warehouse Management (EWM). The system takes into account these prices during the tolerance checks when you post physical inventory documents in EWM and when you post differences to the ERP system.

The report does not always reflect the current prices from the ERP system. Instead, it represents a snapshot of the prices at the time when the report is executed.

We recommend that you execute the report in accordance with the frequency of changes to your product master data. In other words, if your product master data changes frequently, you should also execute the report more frequently.

Operational Reports Create Physical Inventory Document and Create Physical Inventory Document (Cycle Counting) You can use these reports to create physical inventory documents in the background. If you have to count a large number of products, for example, you can have the system create the physical inventory documents overnight and you can then start to process them in the morning.

Print Physical Inventory Count Document You can use this report to schedule the printing of physical inventory count documents as a background job. For example, you can print all the physical inventory count documents for a number of physical inventory documents that you created previously in the warehouse management monitor [Seite 878]. Otherwise, you can schedule the printing as a background job to run overnight.

Post Differences to the ERP System You can use this report to schedule the posting of differences to the ERP system as a background job. As is the case for the Difference Analyzer [Seite 677], you can post differences at cumulative level and detailed level.

The system performs the tolerance check with the user settings for the user who starts the report. If required, create a separate user.

We recommend that you use this report to post small differences.

SAP Extended Warehouse Management (SAP EWM)

510

682

SAP Online Help

20.07.2007

Check Product for Complete Count You can use this report to perform a completeness check in the background. For more information, see Physical Inventory Progress [Seite 680].

Upload Storage Bins and Count Data and Download Storage Bins and Stock Data These reports represent an interface to external systems via which you can upload and download storage bin data and stock data. For uploading, you have the following options: ●

You upload the storage bin data for which you want to carry out a physical inventory. You carry out the physical inventory in EWM.

●

You carry out the physical inventory in an external system and then upload the results to EWM.

For the sample-based physical inventory, you download the storage bin and stock data. You then determine the sample in an external system. You then carry out the sample-based physical inventory in EWM.

Save the data in the format csv.

Check Reports (Checking Errors) Stock Comparison ERP You can use this report to identify and correct inconsistencies between EWM and the ERP system. Since you perform inventory management for a specific storage bin in EWM unlike in the ERP system where you perform inventory management for a specific storage location, the system always assumes that the stocks in EWM are correct. The system also assumes that you have to correct the stocks in the ERP system where necessary.

Adjust Serial Numbers at Warehouse Number Level For serial number requirement B (Serial Number Requirement at Warehouse Number Level), the system saves the serial numbers [Seite 571] in a global table. When you post differences in the Difference Analyzer that might have occurred in various processes, the system does not automatically delete the serial numbers from this table. We therefore recommend that from time to time you reconcile the data in this table with the serial numbers recorded in the physical inventory. This report suggests serial numbers for deletion that have not been recorded by physical inventory documents in the period in question. You can then delete these serial numbers.

SAP Extended Warehouse Management (SAP EWM)

510

683

SAP Online Help

20.07.2007

Physical Inventory Using Radio Frequency Use You can also enter the count results using a radio frequency (RF) device. In this case, you must not print a physical inventory count document [Extern] or transfer the count results from the physical inventory count document to the system. Moreover, the data is transferred to the system in a timely way.

Prerequisites You have logged on [Seite 790] in the RF environment.

Activities You carry out a physical inventory count and enter the count results in the RF device. The device automatically records the count time and the counter. The remaining steps are the same as for physical inventory without radio frequency. For more information, see Physical Inventory [Seite 667].

SAP Extended Warehouse Management (SAP EWM)

510

684

SAP Online Help

20.07.2007

Labor Management (LM) Purpose Labor Management provides you with a series of functions that help you to plan labor times and resources in your warehouse more effectively, thereby making your warehouse more productive. You use these functions to measure, plan, simulate, and visualize the activities in your warehouse. You can compare and evaluate the performance of your warehouse employees based on engineered labor standards. After executing planned work, you can compare the planned and actual times, and trigger incentives such as bonus payments using a connected HR system. LM enhances the comprehensive warehouse management offered by Extended Warehouse Management (EWM), and was developed as an addition to EWM. LM is service-oriented and uses measurement services in planning, for example. It supports processes such as analytical functions [Seite 739] by providing BI Content for EWM. You can find all the BI objects in InfoArea Extended Warehouse Management (0WM) under Supply Chain Management. You use these for long-term, strategic planning, in addition to the short-term, operational planning that you perform in EWM through planning and simulation. You use the short-term operational planning to define calculated planning goals, based on the workload, employees in the warehouse, and the calculated measurement service.

Implementation Considerations You use LM in conjunction with Extended Warehouse Management. For more information about EWM, see SAP Extended Warehouse Management (SAP EWM) [Seite 1]. For more information about using analytical functions, see Analytical Functions [Seite 739].

Features The following functions are available in LM: ●

LM-specific master data [Seite 688], such as processors, and the formula and condition editors

●

Indirect labor [Seite 698] for recording additional work

●

Defining engineered labor standards [Seite 704]

●

Creating planned and executed workload [Seite 713]

●

Labor Management in the warehouse management monitor [Seite 720]

●

Performing operational planning [Seite 728]

●

Employee performance [Seite 732]

SAP Extended Warehouse Management (SAP EWM)

510

685

SAP Online Help

20.07.2007

Activating Labor Management (LM) Use You activate Labor Management for: ●

A warehouse number

●

Internal storage process steps

●

External storage process steps that are relevant for your warehouse

Many functions specific to Labor Management are only possible for those external process steps that you have activated for Labor Management.

If an entry is missing for an external process step, and if the related internal process step is active, the external process step is also active. If no entry exists in the table for activating internal process steps, the internal process step and all the external process steps assigned to it are inactive.

Prerequisites You have activated Labor Management in Customizing for EWM. In the Implementation Guide (IMG) for EWM, choose Labor Management → Activate Labor Management. 1. You activate Labor Management for a warehouse number. 2. You activate Labor Management for internal process steps. In doing so, you simultaneously activate all external process steps assigned to the individual, active, internal process steps. 3. You deactivate those external process steps that are no longer to be active for Labor Management. 4. You have maintained processors [Seite 689] in resource management. Here, you have activated Labor Management for the external process steps of a warehouse number for which you want to create planned and executed workload.

Features The functions specific to Labor Management are: ●

Creating planned and executed workload [Seite 713]

●

Creating performance documents for employees [Seite 738] and connecting an HR system

●

Performing planning [Seite 728] / simulation [Seite 731] and preprocessing [Seite 722]

●

Creating documents for indirect labor tasks [Seite 698]

●

Calculating planned execution times using engineered labor standards [Seite 704]

Example LM is active for: ●

Warehouse number 0001

SAP Extended Warehouse Management (SAP EWM)

510

686

SAP Online Help ●

20.07.2007

For internal process steps Warehouse-Internal Movements, Picking, Loading, Deconsolidate and VAS Activities

LM is inactive for all other internal process steps. For warehouse-internal movements and VAS activities, a more finely-tuned control exists at external process step level. LM is not active for the steps Oiling and Unplanned Movements, but all other external process steps are active. The following figure shows the levels at which LM is active and inactive:

Warehouse number 0001 LM active

;

;

†

;

†

;

LM active

†

†

; ;

Whse-Decon- Quality VAS internal Picking Packing Loading Unload. Invensolid- inspecActiv-move tory ate tion ities ment

LM inactive

Replenishment †

Unpl. movmt ;

SAP Extended Warehouse Management (SAP EWM)

Painting †

Oiling ;

510

687

SAP Online Help

20.07.2007

Master Data in Labor Management (LM) Use The master data described here is specific to Labor Management.

Integration You are using Labor Management to enhance an EWM system that is already in use. LM also uses the master data defined in the EWM system. For more information about EWM master data, see Warehouse Structure [Seite 21] and SCM Basis Master Data [Extern]. You maintain the processor master data on the SAP Easy Access screen for SCM Basis, under Master Data → Resource → Processor, or on the SAP Easy Access screen, under Extended Warehouse Management → Master Data → Resource Management → Processor.

SAP Extended Warehouse Management (SAP EWM)

510

688

SAP Online Help

20.07.2007

Processor Use You use this function to map your employees in the warehouse. You create your employees using the SAP Business Partner, and define master data for the processor [Extern].

Integration Processes are relevant for all processes in the warehouse for which you have activated Labor Management.

Prerequisites 1. You have defined a business partner role for processors in SAP Customizing. For this, use BP role type LM0001 and BP view LM0001. In the Implementation Guide (IMG) for SAP Customizing, choose Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Business Partner Roles → Define BP Roles. 2. In Customizing for SCM Basis, you have defined an HR system and one or more wage types for each HR system, if you want to forward the data to an HR system. In the Implementation Guide (IMG) for EWM, choose SCM Basis → Master Data → Resource → Processor → Make Settings for the HR System. 3. You have sufficient authorization for creating the business partner with BP role type LM0001 for the processor.

Activities 1. To manage the processor data, create a business partner with BP role processor for each employee in the warehouse. On the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Resource Management → Processor → Create Processor. You define the LM-specific attributes on the tab page LM Attributes. a. If you have connected an SAP HR system, assign the processor’s HR personnel number to the processor, enter the HR system, and define a supply chain unit. b. If you want to plan employees, assign to each employee the warehouse number, standard activity area, standard process step, and external storage process steps in which the processor is to work. 2. If you want to work with groups, use the group concept in the SAP Business Partner: a. Create a processor group in business partner Group. Link the processors to the corresponding group using a relationship. Here, use relationship type is processor of (from the view of the processor) or has the processor (from the view of the group). b. You map the group leader in the system as a business partner with the type Person. c. Link the group leader to the corresponding groups using a relationship. Here, use relationship types is group leader of / has group leader For more information about the SAP Business Partner concept, see SAP Business Partner [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

689

SAP Online Help

20.07.2007

If the processor wants to work with radio frequency, you have to enter under Display in BP Role the business partner role you defined for the processor, and then in group box Employee Data on tab page Identification you must enter the user name, to create a connection between the processor and the system user. In the warehouse management monitor you can perform mass maintenance for the processors. To do so, in the warehouse management monitor choose Resource Management → Processor. Select the processors and choose one of the defined methods, such as assigning to a group.

SAP Extended Warehouse Management (SAP EWM)

510

690

SAP Online Help

20.07.2007

Formula and Condition Editor Use You can use this function to define or change formulas [Extern] and conditions [Extern] that you then use in the following functions: ●

Preprocessing [Seite 722]

●

Planning [Seite 728] and Simulation [Seite 731]

●

Engineered Labor Standards [Seite 704]

Formulas and conditions can be part of other formulas and conditions if: ●

They belong to the same formula or condition type

●

The formula is not part of itself (recursive)

●

The formula or condition is active

By using formulas or conditions in other formulas or conditions, you can use these in the warehouse as general parameters, for example to always plan with a weight > 3.

Prerequisites In Customizing, you have activated Labor Management. For more information, refer to the Implementation Guide (IMG) for EWM under Labor Management → Activate Labor Management.

Features In the formula or condition editor, you can create, change, copy and delete formulas and conditions. You define a formula or condition using: ●

A four-digit number

●

Description

●

Formula or condition type details The formula or condition type decides which fields you can use for the formula or condition, and whether the formula or condition is valid for preprocessing, planning, or calculating the engineered labor standards.

Conditions for the preprocessing item and formulas for planning goals also require an external process step. This identifies the formula or condition that the planning or preprocessing uses for a particular step. Formulas and conditions are connected to the transport system. They are transported as Customizing transports. The transport is optional for planning goals; for all other formulas and conditions, it is client-specific. If you have set the indicator Include in Transport Request for a planning goal, you can no longer delete it. You can set the active indicator in the formula or condition. The system only considers active formulas or conditions in preprocessing, planning, or engineered labor standards.

SAP Extended Warehouse Management (SAP EWM)

510

691

SAP Online Help

20.07.2007

When saving the formula or condition, the system checks the correctness of its syntax. If the formula or condition is not correct, the system automatically sets the indicator to inactive, and issues an error message. You can also specify units of measure in the header of the formula or condition. By default, the system uses the units that you have defined for the warehouse number in Customizing for EWM. You can also use a different unit of measure here.

Activities You define formulas and conditions on the SAP Easy Access screen, by choosing Extended Warehouse Management → Settings → Labor Management → Condition Editor or Formula Editor. Formulas and Conditions in Labor Management Function

Use

Type

Use

Preprocessing

Condition for preprocessing header

B

Defines the corresponding settings for preprocessing

Preprocessing

Condition for preprocessing item

A

Defines the corresponding settings for preprocessing

Engineered labor standards

Condition

D

Condition for the engineered labor standards settings

Engineered labor standards

Mathematical formula

E

Formula for calculating engineered labor standards

Planning and simulation

Mathematical formula

F

Defines a planning goal for planning and simulation

Example Example of a Planning Goal ●

Formula 0001: total cost

●

Ext. step: PICK

●

Formula type: F Planning goal

●

Weight unit: KG

●

Unit of length: M

●

Volume unit: M3

●

Unit of time: MIN

Formula: (Planned duration of a workload record * fixed costs per minute * 100 ) / performance level

The system uses this planning goal to calculate the total cost for external step PICK. This formula consists of the: ●

Planned duration of workload record, which the system receives from the workload

●

Fixed costs per minute, which are determined using a calculated measurement service

●

Performance level that is specified in the processor

SAP Extended Warehouse Management (SAP EWM)

510

692

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

693

SAP Online Help

20.07.2007

Formula Editor Use You use this function to define formulas [Extern]. You assign a formula type to a formula.

Formula Types ●

Formula for engineered labor standards [Seite 704] (formula type E) The system uses this formula to calculate engineered labor standards.

●

Formula for planning [Seite 728] and simulation [Seite 731] (formula type F) The system uses this formula to calculate the data determined in the planning for the values defined by the customer.

Features When defining your formulas, you can also use fields as operands. The following list gives you an overview of the defined structures. Each structure contains the fields that you can use for the respective functional area.

Engineered Labor Standards (ELS) (Formula Type D) ●

Workload: /SCWM/S_WRKL_FE_CE

●

Packaging specification: /SCWM/S_LM_PACKSPEC

●

Product: /SCWM/S_LM_PRODUCT

●

Warehouse order: /SCWM/WHO

●

Other formulas for ELS

Planning Goals (Formula Type E) •

Workload: /SCWM/S_WRKL_FE_CE

•

Processor: /SCWM/S_LM_PROCESSOR_FE

•

Other planning goals

•

Calculated measurement service

Example Example of a Formula for Engineered Labor Standards (ELS) ●

Formula: 0002 Duration of execution

●

Formula type: E Formula for engineered labor standards

●

Weight unit: KG

●

Unit of length: M

●

Volume unit: M3

●

Unit of time: MIN

Formula: Planned duration of a workload record + travel time + 5

SAP Extended Warehouse Management (SAP EWM)

510

694

SAP Online Help

20.07.2007

This formula calculates the execution duration of an activity. It contains: ●

Planned duration of a workload record

●

Required travel time for getting to the location of the execution

●

Plus a fixed time of 5 minutes

SAP Extended Warehouse Management (SAP EWM)

510

695

SAP Online Help

20.07.2007

Condition Editor Use You use this function to define or change conditions [Extern]. You assign a condition type to a condition.

Condition Types ●

Condition for engineered labor standards [Seite 704] (condition type D) This condition determines whether a step in the definition of the engineered labor standards is relevant within the current process.

●

Condition for the preprocessing [Seite 722] item (condition type A) This condition determines whether a step in the definition of the preprocessing item is relevant for the current processed delivery item.

●

Condition for the preprocessing header (condition type B) This condition determines whether a storage process in the definition of the preprocessing header is relevant for the current processed delivery item.

Features When defining your conditions, you can also use fields as operands. The following list gives you an overview of the defined structures. Each structure contains the fields that you can use for the respective functional area.

Condition for Preprocessing Header (Formula Type A) ●

Packaging specification: /SCWM/S_LM_PACKSPEC

●

Product: /SCWM/S_LM_PRODUCT

●

Delivery item: /SCWM/S_LM_PPR_DLVI_STR

●

Other conditions for the preprocessing header

Condition for Preprocessing Item (Formula Type B) ●

Packaging specification: /SCWM/S_LM_PACKSPEC

●

Product: /SCWM/S_LM_PRODUCT

●

Delivery item: /SCWM/S_LM_PPR_DLVI_STR

●

Other conditions for the preprocessing item

Condition for Engineered Labor Standards (ELS) (Formula Type C) ●

Workload: /SCWM/S_WRKL_FE_CE

●

Packaging specification: /SCWM/S_LM_PACKSPEC

●

Product: /SCWM/S_LM_PRODUCT

●

Warehouse order: /SCWM/WHO

●

Other conditions for ELS

SAP Extended Warehouse Management (SAP EWM)

510

696

SAP Online Help

20.07.2007

Example Example of a Condition for Engineered Labor Standards (ELS) ●

Condition 0003: Step dependent on volume

●

Condition type C: Condition for engineered labor standards

●

Weight unit: KG

●

Unit of length: M

●

Volume unit: M3

●

Unit of time: MIN

Condition: Volume > 50 In the engineered labor standards, the system uses the condition to determine which formula or constant time is valid for a step. Here, the external step is dependent on the volume of the product being processed, as you use a smaller and quicker resource for a volume less than 50m³ than for a volume of more than 50 m³. This leads to different times for the same step.

SAP Extended Warehouse Management (SAP EWM)

510

697

SAP Online Help

20.07.2007

Indirect Labor Use You can use this function to record activities that do not have anything to do with the actual activities in the warehouse such as picking or putaway. An example of this is sweeping the yard. You can use indirect labor [Extern] to record all activities of your employees in the system without any gaps. You record indirect labor in the system using indirect labor tasks. For each indirect labor task confirmed, the system automatically creates a document for executed workload. This enables you to evaluate indirect labor tasks in the warehouse management monitor, and to create performance documents.

Integration No other functions are required to be able to record indirect labor tasks.

Prerequisites 1. You have activated order document management for indirect labor tasks in Customizing for EWM for each client. In the Implementation Guide (IMG) for EWM, choose Labor Management → Activate Order Document Management for Indirect Labor Tasks. 2. You have activated Labor Management at warehouse-number level and for internal process step INDL (indirect labor). You have also maintained external process steps for internal process step INDL. For example, HOKE for routine tasks, MAIN for maintenance tasks, MEET for meetings. You can define any number of external process steps to be used in indirect labor tasks in Customizing. In the Implementation Guide (IMG) for EWM, choose Labor Management → Activate Labor Management. 3. In the business partner, you have created the processors for which you want to record indirect labor tasks. On the SAP Easy Access screen, choose SCM Basis → Master Data → Resource → Processor. 4. If you are processing indirect labor tasks in the RF environment, you have defined the User Name field for the processor in the employee data on the Identification tab page. On the SAP Easy Access screen, choose SCM Basis → Master Data → Resource → Processor. 5. You have created a number range interval for indirect labor tasks. In the Implementation Guide (IMG) for EWM, choose Labor Management → Determine Number Range for Indirect Labor. ○

If you want to create indirect labor tasks for groups, you have to define an internal number range interval.

○

If you only want to use individual indirect labor tasks, you can also use an external number range interval.

6. If you are working with exception codes for indirect labor tasks, you have to define corresponding exception codes. In the Implementation Guide (IMG) for EWM, choose Cross-Process Settings → Exception Handling → Definition of Exception Codes.

SAP Extended Warehouse Management (SAP EWM)

510

698

SAP Online Help

20.07.2007

○

You use business context IL0 Indirect Labor Task.

○

The execution step for the desktop for exception codes is A1 Desktop Unspecified.

○

The execution step in the RF environment for exception codes is A2 RF Unspecified.

○

The exception codes for indirect labor tasks do not require internal process codes.

○

You can connect indirect labor to the workflow using internal structure /SCWM/S_ILT_INT.

Features You call the function from the SAP Easy Access screen, by choosing Extended Warehouse Management → Labor Management → Maintain Indirect Labor Task. ●

You can use the enhanced search to make selections for one or more indirect labor tasks, such as for the warehouse number or the assignment key. When creating indirect labor tasks for a group, the group responsible can define an assignment key which they can later use, for example, to select indirect labor tasks belonging to this assignment key, by way of a collective confirmation.

●

●

You can create indirect labor tasks for groups, such as for team meetings or for individual processors: o

The processor can subsequently record indirect labor tasks in the system, which he has executed during the course of the day.

o

A group responsible can record indirect labor tasks for his or her employees in the system, which the employees can then complete and confirm in the system.

Employees and group responsibles can change, select, and display indirect labor tasks if they have the required authorization and if the indirect labor task does not yet have the status Completed. You can delete any indirect labor tasks that were not processed. You can no longer delete indirect labor tasks that have the status Completed. You can archive indirect labor tasks.

●

Perform mass changes You can simultaneously set the start and end times for multiple indirect labor tasks. For example, a group responsible can select the relevant indirect labor task at the end of a group meeting, and set the end time and therefore the status Completed for everyone collectively.

●

Record start and end time For indirect labor tasks, you can set start and end times either by entering them manually, or by choosing a pushbutton. The status is set to In Process or Completed.

●

You can set the status for indirect labor tasks. If the status In Process is selected, the start time is set at the same time. If the status Completed is selected, the end time is set at the same time.

●

You can create a note, to specify an instruction for the indirect labor task, for example.

●

You can specify an activity area for the indirect labor task, for evaluation purposes and for location details that define the execution location.

SAP Extended Warehouse Management (SAP EWM)

510

699

SAP Online Help ●

20.07.2007

If a warehouse executes activities for multiple parties entitled to dispose, it may be important to know for which party a particular indirect labor task was performed. You can use the planned execution duration to create an indirect labor task for correction purposes, through which you can “credit” an employee with planned time.

While processing a pick order, an employee encounters problems with his or her resource (fork lift), meaning that he or she significantly exceeds the planned time. To compensate for this surpassed planned time, you can create an indirect labor task with external process step KORR for corrections, and record a planned time over the difference between actual and planned time of the pick order, and set the status to Completed. This credits planned time to the employee, which was missing in his or her pick task without it being his or her fault. ●

If an exceptions occurs while processing an indirect labor task, for example, if a tool for a particular maintenance activity breaks, the employee can input an exception code in the indirect labor task. You can evaluate the exception codes in the warehouse management monitor. You define the exception codes that you want to use for indirect labor tasks in Customizing for EWM.

Indirect Labor Tasks in the Warehouse Management Monitor ●

You can use the warehouse management monitor to select and evaluate indirect labor tasks according to the available selection criteria. You can also branch to the function Maintain Indirect Labor Task. In the warehouse management monitor, choose Documents → Indirect Labor Task or Labor Management → Indirect Labor Task.

●

Using the warehouse management monitor, you can select exceptions according to the available selection criteria that you recorded for indirect labor tasks. Here you can also branch to the reference document for which you have recorded the exception. To do so, in the warehouse management monitor choose Alert → Exception.

Example Example 1 A group responsible creates an indirect labor task for his employees. The activity that is to be done is “sweep yard“. The affected employee selects the indirect labor tasks defined for him or her either on the desktop or using RF, and either sets the status to In Process or enters a start time. After completing the task, the employee sets the status to Completed or enters the end time.

Example 2 At the end of a working day, an employee calls the function for processing indirect labor tasks, and records the indirect labor tasks that he or she has completed during the course of the day. The employee creates an indirect labor task for activity routine work, from 8:00 – 8:30, a period in which he or she charged their fork lift battery. In addition, after completing their pick orders, this employee spent half an hour between 11:30h – 12:00h sweeping the yard. The employee also creates an indirect labor task for this. For the rest of the day, the employee has executed workload documents for the pick warehouse orders they have completed. This means that the employee has seamlessly documented everything he or she has done during the entire working day.

SAP Extended Warehouse Management (SAP EWM)

510

700

SAP Online Help

20.07.2007

Indirect Labor Tasks Using Radio Frequency Use You can also execute indirect labor tasks in a radio frequency (RF) environment.

Prerequisites You have logged on [Seite 790] in the RF environment.

Activities You create indirect labor tasks. Alternatively, you process the indirect labor tasks created for you by selecting these, setting a status, or entering the start time. After completing the tasks, you set the status to Completed or enter the end time. For more information about indirect labor tasks, see Indirect Labor [Seite 698].

SAP Extended Warehouse Management (SAP EWM)

510

701

SAP Online Help

20.07.2007

Function Key Settings for Indirect Labor Tasks in the RF Environment Features Transaction-Specific Function Keys ●

If you have created a note for an indirect labor task, the system displays an X in the RF transaction, next to the number of the indirect labor task. You can display the note using F9.

●

When confirming an indirect labor task, you can enter a defined exception code, or display a list of available exception codes by choosing LIST. You enter the exception code number in the Entry field. You save the exception code and indirect labor task by choosing F4. The information about the exception codes is then available to you to use for evaluation purposes.

●

After a system user calls the RF transaction, the system selects all indirect labor tasks that have been created for this user in this warehouse number and have not yet been completed. The system displays the indirect labor tasks by creation date.

Create Indirect Labor Tasks Pushbutton

Description

F3

Creates new indirect labor tasks for the processor logged onto the RF environment.

F8

Input help for the fields Process Step and Activity Area. For this, the cursor must be placed on the respective field. After that, the cursor then jumps to the next non-filled field when you choose Enter. Specifying an activity area is optional.

F1

Enables you to enter a start time; the status is set to In Process. The status is not visible in the RF transaction, however it is displayed implicitly through the start time. You can only enter an end time when you have entered a start time.

F2

Enables you to enter an end time; the status is set to Completed. The status is not visible in the RF transaction, however it is displayed implicitly through the end time. You can only enter an end time when you have entered a start time.

F4

Saves the indirect labor task. You can only save indirect labor tasks after you have entered an external process step.

Process Indirect Labor Tasks Pushbutton

Description

SAP Extended Warehouse Management (SAP EWM)

510

702

SAP Online Help

20.07.2007

F1

Enables you to set the start time. For the start time, the system sets the system time at the moment when the function key is pressed. When the start time is set, the status of the indirect labor task is set to In Process. You can only set the start time once. After that, you have to change it manually.

F2

Enables you to set the end time. For the end time, the system sets the system time at the moment when the function key is pressed. The status is set to Completed. You can only set the end time once. After that, you have to change it manually, however you can only do this if the end time has not yet been saved. After that, it disappears from the worklist and can only be archived.

F3

Enables you to create a new indirect labor task. The systems keeps changes made to existing indirect labor tasks in the buffer. Choosing F4 saves these to the database together with the newly created indirect labor tasks.

F4

Saves changes made to existing indirect labor tasks, and newly created indirect labor tasks.

F5

Displays the next pushbuttons in the sequence (in case of more than four pushbuttons for a screen) An additional function key is available for indirect labor tasks, which only becomes visible once you press F5. It is function key F10.

F10

Deletes the indirect labor tasks that you are currently processing. You must confirm the deletion by choosing F4. This key is no longer visible after starting the RF transaction, as in the standard system for RF transactions that have a screen size of 8*40, only 4 function keys can be displayed at the same time. If a transaction contains more than 4 function keys, this is displayed to you through a ”greater than“ (>) character next to F4. For indirect labor tasks, function key F10 is displayed when you press F5. You can also choose F10 even if it is not currently visible.

SAP Extended Warehouse Management (SAP EWM)

510

703

SAP Online Help

20.07.2007

Engineered Labor Standards Use You use this function to define the times that are required to execute an activity in the warehouse. The system calculates engineered labor standards (ELS) when: ●

Creating a document, when the system generates planned workload

●

Confirming a document, when the system generates executed workload

The system saves the labor standards in the planned workload as planned duration, and in the executed workload as an adjusted planned duration. The final data is only available when you have confirmed the document, as only then is the executing resource known and therefore also the: ●

Speed of the resource

●

Last position of the resource prior to executing the activity

●

Travel distance allowed for the resource

The system uses this additional data for the travel distance calculation. It saves the results of the travel distance calculation in the planned and executed workload. You can include a formula or condition as parameters when defining the engineered labor standards. When calculating the planned time of the planned workload, the system estimates the following information: ●

For the speed, the system uses the slowest resource (pessimistic approach).

●

Instead of using the exact position of the resource, the system uses the default distance. The default distance is the distance traveled to reach the first item of a storage type.

●

The route network, which contains all defined routes without resource type restrictions.

The calculated planned time is used for the following: ●

Operational planning of the planned workload

●

Evaluating employees by comparing the measured time with the planned time stored in the workload

BAdI /SCWM/EX_ELS You can influence the results of the engineered labor standards in BAdI /SCWM/EX_ELS, in enhancement spot /SCWM/ES_ELS, by using the following two methods: ●

START_DEFAULT You can use this method to deactivate the implementation for engineered labor standards delivered in the standard SAP system. This may be appropriate for performance reasons if the calculation is done customer-specifically.

●

CHANGE_ELS_RESULT You can use this method change or overwrite the result (planned time, unit of time) of the ELS calculation.

For more information about this BAdI, see the Implementation Guide (IMG) for EWM under Business Add-Ins (BAdIs) for Extended Warehouse Management → Labor Management → Engineered Labor Standards → BAdI: Changing Standard Time Determination.

SAP Extended Warehouse Management (SAP EWM)

510

704

SAP Online Help

20.07.2007

Integration ●

To save the ELS result in the planned and executed workload, you have activated Labor Management.

●

You can use the result of the travel distance calculation for the engineered labor standards.

●

You can use the planned time calculated via the engineered labor standards in operational planning.

●

You can evaluate employees by comparing the adjusted planned time with the actual execution duration.

Prerequisites ●

You have activated Labor Management.

●

You have defined formulas in the formula editor and conditions in the condition editor.

●

You have define engineered labor standards in Customizing for EWM, by choosing Labor Management → Determine Engineered Labor Standards.

SAP Extended Warehouse Management (SAP EWM)

510

705

SAP Online Help

20.07.2007

Configuring Engineered Labor Standards (ELS) Use You use this function to configure engineered labor standards. You split up an activity into work steps, which the warehouse worker must execute sequentially, which make up a work step sequence. The planned time for the activity is then made up of the total of all planned times of the individual work steps in the work step sequence. The system uses a wildcard function to assign a work step sequence to an activity. You use either a constant or a formula to determine the planned time of a work step. You can make multiple entries for these, and use conditions to define the ones you want to be use for the calculation. The fields that you use in the formulas and conditions are dependent on the object type for which you are defining engineered labor standards. This means, for example, that it is not possible to use product information to calculate the ELS of a warehouse order directly, as this may collect warehouse tasks that have different products.

Activities You configure engineered labor standards in Customizing for EWM, under Labor Management → Determine Engineered Labor Standards.

1. Define Work Steps Work steps are part of an activity. You can define a sequence of constants or formulas to which you assign conditions. The system goes through the individual sequence steps one by one. It uses the first constant or formula whose assigned condition is “true“. 2. Define Work Step Sequence A work step sequence consists of work steps or other work step sequences. The resulting sequence of work steps must be executed sequentially. The planned time of the work step sequence is the total of the planned times of each related work step. 3. Assign Work Step Sequences You assign the following to the work step sequence: ○

Warehouse number

○

Object type

○

External process step

○

Activity area

The system uses the wildcard function. If the system fails to find an entry for one of the objects listed above, it looks for an assignment without an activity area. If this does not exist either, the system looks for an assignment with warehouse number and object type. 4. Assign Formulas and Conditions The following shows you which object types you can assign to which fields: ○

Workload fields are allowed for all object types

SAP Extended Warehouse Management (SAP EWM)

510

706

SAP Online Help

20.07.2007

○

Fields for the product are allowed for the object types warehouse task, physical inventory item, HU item, delivery item, and VAS activity

○

Fields for the Packaging specification are allowed for the object type VAS activity

Direct ELS Definition If a work step sequence consists of just one work step, and if you actively assign this only once using Assign Work Step Sequence, you can use the Direct ELS Definition. In this, you assign the engineered labor standards directly. The system generates the required work step and work step sequence automatically.

SAP Extended Warehouse Management (SAP EWM)

510

707

SAP Online Help

20.07.2007

Uploading Engineered Labor Standards (ELS) Use You can use this function to upload engineered labor standards from another external system. There are two ways to copy existing data: ●

By uploading a local file, such as a Comma-Separated-Values file (CSV file).

●

By uploading a file from an application server. In this case, Extended Warehouse Management (EWM) uses a connection to the Legacy System Migration Workbench (LSMW). For more information about the LSMW, see SAP Library under mySAP ERP → SAP Oil & Gas → SAP Oil & Gas (IS-Oil Downstream) → Integration of SAP Oil & Gas with SAP CRM → F&A Pricing in Integration with SAP CRM → Legacy System Migration Workbench.

You can upload existing data for the following objects in Labor Management: ●

Formula or condition

●

Work step

●

Labor standard of the work step

●

Work step sequence

●

Assignment of work step sequence

Prerequisites The CSV file as a header line and the following column format Formula or condition LGNUM

PROCS

FORMULA

FORMULA_TYPE

VALID

Char 4

Char 4

Char 4

Char 1

Char 1

Formula or condition WGT_UOM

VOL_UOM

DIST_UOM

TIME_UOM

FORMULA_TXT

FORMULA_ELEMENT

Char 3

Char 3

Char 3

Char 3

Char 40

Char 100

Work step LGNUM

STEP

DESCRIPTION

Char 4

Char 4

Char 40

Labor standard of the work step

SAP Extended Warehouse Management (SAP EWM)

510

708

SAP Online Help

LGNUM

STEP

20.07.2007

NUM

CONDI

CONSTANT

UNIT

FORMULA

ACTIVE

Char 16

Char 3

Char 4

Char 1

TION Char 4

Char 4

Char 5

Char 4

Work step sequence LGNUM

SEQUENCE

NUM

STEP

SEQUENCE (included)

ACTIVE

Char 4

Char 4

Char 5

Char 4

Char 4

Char 1

Assignment of work step sequence LGNUM

PROCS

ACTIVITY AREA

OBJECT TYPE

NUM

SEQUEN CE

ACTIVE

Char 4

Char 4

Char 4

Char 1

Char 5

Char 4

Char 1

The LSMW uses the following structures: ●

/SCWM/S_ELS_LSMW_FRML – Formula or condition

●

/SCWM/S_ELS_LSMW_ST – Work step

●

/SCWM/S_ELS_LSMW_STE – Labor standards of the work step

●

/SCWM/S_ELS_LSMW_SEQ _ - Work step sequence

●

/SCWM/S_ELS_LSMW_ASS – Assignment of work step sequence

Activities You call the function from the SAP Easy Access screen, by choosing Extended Warehouse Management → Settings → Labor Management → Upload Engineered Labor Standards.

1. Specify the type of host from which you want to upload the file: ○

From a local computer

○

From an application server

2. Use the Delete Existing Data field to select whether the uploaded data is allowed to overwrite existing settings. 3. Enter the file name and choose Upload. The system uploads the data and displays it on the tab page Loaded Data. If you are working with a file on an application server, the data is fetched from the application server, and the system displays it to you. 4. Make corrections if required.

You are using a local CSV file A. After the system has uploaded file A and is showing you the data, you notice that the formatting of the Excel file is incorrect. You correct the formatting and upload the file again. If you upload a file from an application server, you can make corrections directly in the LSMW and then upload the file again.

SAP Extended Warehouse Management (SAP EWM)

510

709

SAP Online Help

20.07.2007

5. Choose Execute with the quick info Start Data Transfer. The system stores the data to the database. On the Successful Changes tab page, you can find all the data that has been successfully created. On the Failed Changes tab page, you can find all the data that EWM was unable to create. The column Message on this tab page also shows you the additional message text.

SAP Extended Warehouse Management (SAP EWM)

510

710

SAP Online Help

20.07.2007

Example for Engineered Labor Standards

d

d

d

d

d

A warehouse manager has created a warehouse order with multiple warehouse tasks. One of the warehouse managers must fetch various toys and a cardboard box for packaging from the warehouse. The calculation of the planned time must consider the following: ●

Individual withdrawal processes

●

Travel distances

●

Constant time for reading the warehouse order

The following must apply for the calculation: ●

The planned time of the warehouse order corresponds to the sum of the planned times of the warehouse tasks + travel time + constant.

●

The planned time of a warehouse task must be independent of the product group (for example, toy, packaging).

●

For a withdrawal process, the steps turn, take and put on resource apply, whose times are partially constant. The step take depends on the weight.

The warehouse manager makes the following settings for the warehouse order: ●

As a formula, he creates a sum with the following addends: ○

Planned time of workload (to use the planned times of the warehouse tasks)

SAP Extended Warehouse Management (SAP EWM)

510

711

SAP Online Help ○ ●

20.07.2007

Travel time

He defines the two work steps: ○

Read Document: with a constant for the time calculation

○

Execute Labor Tasks: with the previously defined formula for the time calculation

●

He defines the work step sequence, consisting of the two work steps.

●

He assigns the defined work step sequence to the following objects: ○

Warehouse number

○

External process step

○

Activity area

○

Object type Warehouse Order for Warehouse Tasks

He makes the following settings for the warehouse task: ●

He creates a formula for the planned time calculation of work step Take as a product of the weight and a constant, such as 1 kg corresponds to 3 minutes of planned time.

●

He defines the condition using the given product group Toy.

●

He defines the work steps: ○

Turn: with a constant for the time calculation

○

Take is defined for the toys using the formula for the time calculation, and for the packaging using a constant. The defined condition controls the different calculation.

○

Put on resource: with a constant for the time calculation

●

He defines the work step sequence, consisting of the three work steps.

●

He assigns the defined work step sequence to the following objects: ○

Warehouse number

○

External process step

○

Activity area

○

Object type Warehouse Task

SAP Extended Warehouse Management (SAP EWM)

510

712

SAP Online Help

20.07.2007

Planned and Executed Workload Use The system uses this function for each external process step and activity area [Extern] to automatically create a document for the planned workload [Extern]. You use this document [Extern] as a basis for planning your resources. After performing the work, you can use the executed workload to compare the planned and actual durations. You can forward the result of your evaluation to an HR system, using a performance document [Extern], to trigger payment of a bonus, for example. Each task in the warehouse has a certain workload. You can only plan this workload if the scope of the task involved is fixed, for example, if a warehouse order that has various warehouse tasks has been created. After executing the work, additional data is then available, such as which worker executed the work, the exact start and finish time, and the resources used. In the executed workload, you can compare the planned and actual duration for: ●

Warehouse orders [Extern]

●

Value-added service orders [Extern]

●

Quality inspection documents

●

Physical inventory documents [Extern]

●

Indirect labor [Extern]

You can use the information contained within the planned workload document to make strategic decisions. For example, this enables you to use the total of all planned activities in a particular activity area, on a particular day, to plan the number of employees for this day, in this activity area. In a similar way, you can use the information in the executed workload to compare the performance of individual employees and groups, and to forward this data to a connected HR system to trigger payment of a bonus, for example. To do this, you must create a performance document for an employee for a particular evaluation period.

Prerequisites In Customizing for EWM under Labor Management → Activate Labor Management, you have activated Labor Management for the warehouse number and the external process steps for which the system creates planned and executed workload documents.

Features External Process Step As you control Labor Management using external process steps, each document or document item must have an external process step assigned to it. The assignment depends on the document: Warehouse Orders Using Storage Control For warehouse tasks for storage control, the external process step is determined from the profile in the storage control. For each step defined in the profile, the system creates a data record for the planned workload, even if no document exists yet for this step. Exceptions to this are optional steps, such as deconsolidation. In this instance, the system only generates the workload records when it's clear than the step is also performed.

SAP Extended Warehouse Management (SAP EWM)

510

713

SAP Online Help

20.07.2007

For the steps in the storage control profile for which a document is created, the planned workload record of the storage control is deleted, and a planned workload record is created for the document, as this contains more precise information. Other Warehouse Orders For warehouse orders for warehouse tasks that were not created through storage control, or for physical inventory warehouse orders, the external process step is determined using the activity. You can assign an external process step to an activity in Customizing for EWM. In the Implementation Guide (IMG) for EWM, choose Labor Management → Define Activities. You define new process steps in Customizing for EWM under Labor Management → Define External Process Steps. For the internal process step, you can select NSCT for movements that are not storage-control-relevant, or INVE for physical inventory, for example. Quality Management (QM) For the workload for inspection documents, the system takes the external process step of the document itself. For this, you have to specify an external process step for the inspection document in the inspection rule. For subordinate elements of the inspection document, the external process step of the inspection document is relevant. This does not apply if an external process step is assigned to the element using a sample-drawing instruction. Value-Added Service Orders (VAS Orders) For VAS orders, you can configure an external process step for each activity. You maintain this in the packaging specification of the VAS order. Indirect Labor The system does not create planned workload for indirect labor, it only creates executed workload.

Activity Area The activity area is defined for warehouse orders using the respective warehouse tasks. For warehouse orders for the physical inventory, the activity area of the physical inventory itself is used. For VAS order and inspection documents, the activity area corresponds to the planning activity area that has been specified for the work center.

Planned Execution Duration The data for the planned execution duration is calculated using the engineered labor standards [Seite 704]. For warehouse orders, the travel distance or travel time can also be included in this calculation.

SAP Extended Warehouse Management (SAP EWM)

510

714

SAP Online Help

20.07.2007

Planned Workload Document Definition The planned workload document contains data relevant for Labor Management, including information about: ●

Activity area

●

Activity (external process step)

●

Quantity (optional)

●

Planned duration calculated using engineered labor standards

●

Planned end date

●

Travel distance, if defined

●

Capacity data, such as weight or volume

After executing the planned work, the system forwards the relevant information to the executed workload document, and then deletes the planned workload document.

SAP Extended Warehouse Management (SAP EWM)

510

715

SAP Online Help

20.07.2007

Executed Workload Document Definition After executing the activity, the system creates a document for the executed workload containing the information for the following details relevant to Labor Management: ●

Reference document that caused the workload (reference object type, ID of the reference document)

●

Activity area

●

Activity (external process step)

●

Planned duration

●

Adjusted planned duration

●

Actual duration

●

Start and end time of the execution

●

Processor

●

Weight, volume, calculated travel distance and calculated vertical travel distance, capacity consumption

●

Number of subordinate items or documents belonging to the reference document

●

Status

The system then deletes the planned workload document.

SAP Extended Warehouse Management (SAP EWM)

510

716

SAP Online Help

20.07.2007

Planned Workload Use The data record for the planned workload contains information about the location of the work, the type, quantity, duration, and capacity. The data record also contains a link to the generating document in the form of an object reference, such as a link to the QM document or warehouse order. You can use the data of all planned workload records in Planning [Seite 728] and Simulation [Seite 731] to determine how much work arises in the individual activity areas, and of which type. As soon as the work has been executed, the system creates a data record for the executed workload, and deletes the data record for the planned workload.

If you have implemented BAdI /SCWM/EX_LM_WRKL_QUAN, you can include the quantity in the planned workload. This does not apply to workload records for VAS activities. In the case of VAS activities, the system sets the quantity. This corresponds to the open quantity of the VAS activity. For more information about this BAdI, see the Implementation Guide (IMG) for EWM under Business Add-Ins (BAdIs) for Extended Warehouse Management → Labor Management → Workload.

Integration The system generates data records for the planned workload as soon as it knows that work has to be executed. This is that case when documents are generated, such as: ●

Warehouse order with warehouse tasks

●

Warehouse order for the physical inventory

●

QM inspection document

●

VAS order

●

Warehouse tasks for storage control

The data of the planned workload records is used in operational planning [Seite 728].

Prerequisites You have defined the required external process steps in Customizing for your warehouse number. For more information, see the Implementation Guide (IMG) for EWM under Labor Management → Activate Labor Management.

SAP Extended Warehouse Management (SAP EWM)

510

717

SAP Online Help

20.07.2007

Executed Workload Use This central document contains all Labor-Management-relevant data that you can use to compare the planned and actual times objectively. While the work is being executed, the system or user records the name of the processor and the start and end time, for example. In addition to the data of the planned workload [Seite 717], the system also stores the changed planned duration after the execution, for example depending on the used resource. A deviation from the planned duration is possible, for example if: ●

Resource types have different speeds

●

A difference quantity results from the order

●

Exceptions were triggered (exception handling)

After completing the activity, the system stores the executed workload. The system automatically deletes the data record for the planned workload. If you confirm a reference document that generates an executed workload, it is given the status Valid. If you change a record that has the status Valid in the warehouse management monitor, the system only sets the status of this record to “invalid“. It writes a new record containing the changes and status Valid. The changed record of the executed workload is marked as manually corrected. If you have implemented BAdI /SCWM/EX_LM_EWRWL_QUAN, you can include the quantity in the executed workload. This does not apply to workload records for VAS activities. In the case of VAS activities, the system sets the quantity. This corresponds to the open quantity of the VAS activity. For more information about this BAdI, see the Implementation Guide (IMG) for EWM under Business Add-Ins (BAdIs) for Extended Warehouse Management → Labor Management → Workload.

SAP Extended Warehouse Management (SAP EWM)

510

718

SAP Online Help

20.07.2007

Interaction Between Performance Document and Executed Workload Use You can use performance documents [Extern] to evaluate executed workload (EWL) cumulatively for each processor. Note the following: ●

The assignment of the EWL to a performance document is based on the processor and on the end of the execution date of the EWL, which lies within the evaluation interval of the performance document.

●

You can no longer create any additional EWLs for the evaluation intervals of an employee’s performance documents once the performance documents have been approved, or if they are currently being changed.

●

If the end date of the EWL does not lie within the evaluation interval of the performance document, or if the performance document has status Created, Deleted or Manually Deleted in display mode, this restriction does not apply.

●

If you change a performance document that has the status Created, For Approval, Approved, Transferred, Manually Transferred, or To Delete, you are unable to create an EWL and assign it to the performance document. If you still attempt to confirm an original document that generates an EWL that conflicts with an existing performance document time-wise, the system issues an error message. This restriction also applies if you change the EWL directly in the warehouse management monitor.

We recommend that you only create a performance document for evaluation intervals in the past. A performance document must only be given the status For Approval, if no further EWL falling within the evaluation interval of the performance document is going to be generated.

SAP Extended Warehouse Management (SAP EWM)

510

719

SAP Online Help

20.07.2007

Labor Management (LM) in the Warehouse Management Monitor Use The processor, warehouse manager, or group leader can use this function to call LM-relevant information in the warehouse management monitor. For example, you can evaluate the efficiency of your employees, or the weight that was moved in a particular activity area in one day. The following nodes are defined: ●

Planned workload The planned workload reflects the work expected in the warehouse. Each data record references an open object that is still to be processed, such as an open warehouse task. You can use the planned workload to perform planning in your warehouse.

●

Executed workload The executed workload reflects the completed work in your warehouse. Each data record references a completed object, such as confirmed warehouse tasks.

●

Labor utilization Labor utilization is the aggregated view of the executed workload. You can use the Efficiency to evaluate the performance of your employees. Under Utilization, you can use the actual data comparison, direct an indirect labor, and attendance of the processor to evaluate the performance of the processor. The data is displayed on three levels.

●

○

The first level contains the aggregated data.

○

The second level is the aggregation by date and processor, for example.

○

The third level is the individual data record of the executed workload.

Indirect labor task

Prerequisites You have assign the authorizations correspondingly. You can adjust the authorization concept so that processors can only display their own work data, group leaders can display the work data if their groups, and warehouse managers can display all relevant warehouse data.

Activities From the warehouse management monitor, you can carry out the following activities: Node

Activities

Planned workload

Branch to reference document

SAP Extended Warehouse Management (SAP EWM)

510

720

SAP Online Help

Executed workload

20.07.2007

●

Change executed workload for the fields: ○

Processor

○

Start data and time

○

End date and time

○

Planned execution duration

After making the changes, you have to call the data again. You can only change executed workload that has the status Valid. Note the restrictions [Seite 719] that apply when changing the executed workload for the performance document. ●

Create indirect labor task

●

Display history

●

Branch to reference document: Branch to handling units, quality inspection documents, warehouse tasks, value-added service orders, waves, or warehouse orders

Labor utilization

Indirect labor task

Drill-down data by: ●

No aggregation

●

Date and processor

●

Date and activity area

●

Date, processor, and activity area

●

External process step

●

Date, party entitled to dispose, and external process step

●

Date and reference

●

Individual records (executed workload)

Branch to indirect labor task

SAP Extended Warehouse Management (SAP EWM)

510

721

SAP Online Help

20.07.2007

Preprocessing Use This function gives you an overview of the workload that arises at a particular time for inbound and outbound deliveries or in the physical inventory for Cycle Counting [Seite 673]. In terms of time, this determination comes before the execution, meaning before you create warehouse tasks and warehouse orders for delivery items or for cycle-counting documents. You can use the result, for example, when planning employees for a particular activity area of for a particular process step. For planning, you define planning goals for your process steps in the formula editor [Seite 694]. The result of the preprocessing is only used for planning purposes; it does not affect the actual execution.

Integration Preprocessing is part of the Planning and Simulation function.

Prerequisites EWM System 1. In the group box Planning Data, you have selected an Object Type for the delivery or cycle counting within the physical inventory: ○

K for delivery item

○

F for warehouse order for physical inventory

2. In the planning function, you have selected the field Use Preprocessing in the Preprocessing group box, by choosing Open Enh. Search. 3. You have defined the planning period in the group box Planning Period.

Features When you make Customizing settings for preprocessing, you can call the condition editor [Extern] in the manual setting and in the wizard. This is then started in display mode, enabling you to view the details of the currently selected condition. If you want to create or change conditions, on the SAP Easy Access screen choose Extended Warehouse Management → Settings → Labor Management → Condition Editor.

Activities On the SAP Easy Access screen, choose Extended Warehouse Management → Labor Management → Planning → Planning and Simulation. 1. As preprocessing is only possible for delivery items or for cycle counting, you must select the key for the delivery item and/or for warehouse order for the physical inventory when calling preprocessing. 2. Call the function Planning and Simulation. Here you can make settings using the enhanced search in group box Preprocessing. ...

○

Read expected goods receipt [Seite 180]: If you select this field, the system also considers the delivery information of the expected goods receipt for preprocessing.

○

Wave [Seite 766]: You can specify waves for preprocessing. The system determines the workload for deliveries that are assigned to the specified waves.

SAP Extended Warehouse Management (SAP EWM)

510

722

SAP Online Help ○

20.07.2007

Percentage: You use this value to define the percentage of deliveries that have already been recorded in the system. For the missing percentage, the system then creates an additional preprocessing for each activity area and each respective external process step. The maximum value that can be entered is 100%. If you enter a value less than 100%, the preprocessing workload is increased by the difference between that value and 100%.

You perform planning based on delivery items. At the time of planning, only 50% of the deliveries have been created in the system. You therefore set the percentage value to 50%. The system adds the remaining 50% to the determined workload. 3. In the group box Planning Period, enter the time period for which you want to create preprocessing. 4. After performing the enhanced search, the system displays the determine workload records for the individual process steps and activity areas. If you look at the detailed information of the workload, you can identify workload records for preprocessing by way of the special workload object type K. If the records involved are workload records for delivery items, the reference documents contain the corresponding delivery items (F).

Example ●

Inbound delivery 4711

●

Delivery date/time: 02.05. 16:00

●

Delivery: Item 10 containing 100 pieces of summer tires. The system finds activity area 0010 and warehouse process type 1011 for this delivery item in EWM Customizing. The warehouse manager has also made these settings for the preprocessing header in Customizing, using activity Set Preprocessing. The system also assigns storage process INB1 for putting away this product.

Preprocessing Header ●

Warehouse number: EEG1

●

Activity area: 0010

●

Warehouse process type: 1011

●

Sequence number: 1

●

Condition

●

Storage process: INB1 (putaway)

Two steps were assigned in the preprocessing item, namely IB01 (unloading) and IB03 (putaway).

Preprocessing Items Sequence Number

Process Step

Activity Area

Percent age

Duration

Unit

IB01 (unloading)

9010 (Staging goods receipt area)

100

30

min.

SAP Extended Warehouse Management (SAP EWM)

510

723

SAP Online Help

IB03 (putaway)

20.07.2007

0010 (high-rack storage area)

100

30

min.

Preprocessing 1. The warehouse manager calls the function Planning and Simulation. 2. He opens the enhanced search, and enters data for the planning. He selects K for delivery item, as the object type. 3. He selects the field Use Preprocessing. 4. For the planning period, he enters 02.05. 16:00 to 02.05. 18:00. 5. He chooses Execute. The system determines the workload. As a result, the warehouse manager receives two data records, one for unloading and one for putaway. From the workload details he can see the respective detailed records. In the detailed area, he can also see that the records refer to delivery 4711, item 10. Result The result shows the warehouse manager which delivery will cause work in the given time period, and in which activity area this work will arise. He assigns planning goals to the individual steps, which preprocessing uses to evaluate the determined workload records.

SAP Extended Warehouse Management (SAP EWM)

510

724

SAP Online Help

20.07.2007

Preprocessing for Deliveries and Physical Inventory Use You use this function to create the workload based on deliveries or physical inventory documents.

Features Delivery When creating the workload, the system determines the process steps required to execute a particular delivery item in the warehouse. You specify these steps in Customizing for EWM under Labor Management → Set Preprocessing. Preprocessing calculates the time when the workload is due, based on the duration of the steps of the found process and of the dates/times of the delivery. You select the data type that you want to use for calculating inbound and outbound deliveries in Customizing for EWM, under Extended Warehouse Management → Labor Management → Define Delivery Date/Time for Preprocessing. The dates/times here are always planned and not actual. If you fail to define a date/time, the system always uses the planned delivery date/time for the time calculation.

Physical Inventory Preprocessing only supports cycle counting within the physical inventory because it takes place periodically, and can therefore be planned. You do not have to make any special settings. The system uses the settings that you have made for the physical inventory. There is only one difference to the physical inventory: If an active cycle counting document exists in which you plan cycle counting for a later time, such as for the following day, preprocessing determines that cycle counting is required again in 31 days, if the specified planning period stretches that far.

Prerequisites EWM Customizing You can make Customizing settings for preprocessing either directly or using a wizard. ...

1. In Customizing, you have activated Labor Management. For more information, refer to the Implementation Guide (IMG) for EWM under Labor Management → Activate Labor Management. 2. You have defined a preprocessing header and preprocessing items. For more information, refer to the Implementation Guide (IMG) for EWM under Labor Management → Set Preprocessing. ...

Preprocessing Header In the preprocessing header, you assign a storage process to a delivery item.

You define a separate storage process with the name of the owner for the products for which you have to execute a special value-added service. You identify the delivery item using the activity area and warehouse process type that the system has found for the delivery item. You can also specify a condition [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

725

SAP Online Help

20.07.2007

Preprocessing Items The entry found by the system in the preprocessing header is the key for determining preprocessing items that are relevant for the current delivery item. In the preprocessing item, you define the steps for preprocessing in the warehouse that are relevant for delivery item currently being processed. ○

Duration: As a standard process, the system takes the duration of the external process step from Customizing for storage control [Seite 334]. You can change this value. The system uses the duration to determine when a step takes place in the warehouse. As a basis for this, it uses the dates/times of the delivery across the duration of all steps of the found process. You can assign a step to a preprocessing item more than once.

If you define identical steps in Customizing one after another, note that the system uses the Percentage field to check the total of the entries in the field. The total of the percentage values must not exceed 100%, otherwise this would mean additional workload. If another step is positioned between two identical steps, the system considers the identical steps as being independent of each other. ○

You can define either a Percentage or a Condition. The percentage value tells you the percentage of the current delivery item that is relevant for the found activity area and found process step. The condition enables you to see in more detail whether a found step is relevant for a delivery item. Here you can make checks based on the attributes of the condition editor [Seite 696]. Only when this check has been performed successfully does the system consider the step for the current delivery item in the preprocessing.

EWM System In the group box Planning and Data of function Planning and Simulation, you have selected an Object Type for the delivery or cycle counting within the physical inventory: ●

K for delivery item

●

F for warehouse order for physical inventory

SAP Extended Warehouse Management (SAP EWM)

510

726

SAP Online Help

20.07.2007

BAdIs for Preprocessing Use You can adjust preprocessing to your requirements using BAdIs. For more information, see Customizing (IMG) for EWM under BadIs for Extended Warehouse Management → Labor Management → Preprocessing.

BAdI /SCWM/EX_PPR_TIME for Changing the Selection Time You can use this BAdI to change the selection time for deliveries that is determined by the system. Here, the system transfers the determined selection time, as well as the relevant preprocessing settings and an indicator for whether the deliveries involved are inbound or outbound. The time determined in this way is later used when selecting the deliveries.

BAdI /SCWM/EX_PPR_WL for Changing the Preprocessing Workload You can use this BAdI to change the preprocessing workload that is determined by the system. After determining the preprocessing, the system transfers all the used inbound and outbound deliveries, as well as the preprocessing settings and the determined workload records. The system forwards the result to planning.

SAP Extended Warehouse Management (SAP EWM)

510

727

SAP Online Help

20.07.2007

Operational Planning Use You use this function to define calculated planning goals based on the workload [Extern], processors [Extern], and a calculated measurement service [Extern] (CMS). You create the planning formula in the formula editor [Seite 694]. A planning formula is valid for one warehouse number and external process step, and is intended for calculating the number of required employees based on the planned workload, for example. The planning is based on: ●

The calculated measurement service (CMS)

●

Aggregated information: ○

Planned workload

○

Planned workload that you created using preprocessing [Seite 722]

○

Information about the processors

Prerequisites ●

You have activated Labor Management with the external process steps that you want to plan. The basis for the planning is planned workload.

●

You have created planning formulas in the formula editor [Seite 694].

Features You call the planning function from the SAP Easy Access screen, by choosing Extended Warehouse Management → Labor Management → Planning → Planning and Simulation.

Selections You select the planned workload using the following: ●

Warehouse number (default value)

●

External process step (using Search and Enhanced Search)

●

Activity area (using Search and Enhanced Search)

●

Object type for which the workload was generated (using Enhanced Search)

●

Planning period (using Enhanced Search)

●

Party entitled to dispose (using Enhanced Search)

You select the Processor using the following: ●

Standard activity area (using Search and Enhanced Search)

●

Standard process step (using Search and Enhanced Search)

You select a planning formula. In the Simple Search, the system arranges the planning formulas into alphabetical order, and takes the formula that occurs first in the alphabetical order.

SAP Extended Warehouse Management (SAP EWM)

510

728

SAP Online Help

20.07.2007

You can select a separate planning formula for each external process step by choosing Enhanced Search → Assign Formula.

You select the calculated measurement service (CMS) using the planning formula. The system only calculates and displays ones that are used in at least one planning formula.

Variants: You can save the parameters of an enhanced search in a variant.

Preprocessing You can create planned workload using the preprocessing [Seite 722], based on the deliveries, expected goods receipt, or the physical inventory.

Planning Planning is an evaluation of the planning formulas. You can perform planning manually by choosing Planning → Evaluate Planning Formula. Alternatively, you can perform planning automatically by choosing Automatic Planning (using Enhanced Search).

Simulation You can change individual planning parameters and then check what effects these have on your planning.

Planning Formula You use planning formulas to define your planning goals. Form planning, you can branch to the formula editor to display the planning formula.

Workload Data You can switch to other transactions to display the respective documents for: (Display Additional Data) ●

Handling units

●

Warehouse tasks

●

Physical inventory

●

Delivery

●

Value-added services (VAS)

●

Quality management

Display Graphic You can display the results of the planning formulas as a graphic.

Simple Display You can restrict the display of the aggregated information to the fields used in the planning formulas, or display all fields.

Message Log The message log contains the error messages. You can call it by choosing Message Log.

SAP Extended Warehouse Management (SAP EWM)

510

729

SAP Online Help

20.07.2007

Save You can save the aggregated information and the calculated measurement services that you use. In addition to the key used by the system (date, user), you can specify a planning variant. You can display the saved data by choosing function Load Planning and Simulation Results (/SCWM/PL_LOAD).

Details In addition to the aggregated data, you can display the calculated measurement services, the individual processors, and the workload.

Activities 1. You create documents and thereby create a planned workload. 2. You execute planning. 3. The system evaluates the planning formula and displays the planning results.

Example The warehouse manager performs planning based on preprocessing that considers deliveries from a wave. He links this to the following three planning formulas: ●

Planning formula that calculates the number of processors: Number of FTEs = Total planned duration / 8 h

●

Planning formula that calculates the number of processors using a key figure: Number of FTEs = Number of workloads / Key figure (number of workloads per processor in the last month)

●

Planning formula that calculates the required hours for a predefined number of processors, while considering the effectiveness of the processors: Total duration = Total planned duration * 100 / Total effectiveness of processors (in %).

SAP Extended Warehouse Management (SAP EWM)

510

730

SAP Online Help

20.07.2007

Simulation of Planning Use You use this function to find out how changes in the planning environment, such as expected workload, would affect the result. You can change the specified data manually, and reevaluate the planning formulas based on this changed data. You can change the aggregated information, such as planned workload and processor, as well as the detailed data of the individually planned workload records, individual processors, and the results of the calculated measurement services. The system only saves these changes temporarily. When you close the transaction, the system discards the changes. After each manual change, the system initializes the result of the planning formula. If you activated automatic planning, the result is calculated again each time a manual change takes place.

Features You can: ●

Create simulation data

●

Delete simulation data

●

Undo manual changes

You can use this simulation to manually change the following information that is displayed: ●

Aggregated information of the planned workload and processors The system generates a correction data record in each case, which then logs the changes.

●

Results of the calculated measurement services

●

You can add, delete and copy a processor

●

Information about the planned workload

●

You can select a new planning formula

●

You can change the selected planning formula (choose Display/Change Formula). All changes are only temporary.

SAP Extended Warehouse Management (SAP EWM)

510

731

SAP Online Help

20.07.2007

Employee Performance Use You can use this function together with information in the performance document [Extern] and in the executed workload (EWL) assigned to the performance document to calculate, save and forward performance-related amounts to a connected HR system. If you have connected the EWM system to an SAP ERP HR system (Rel. 4.6C or higher), you can transfer the performance document amount to the HR system as an external wage component [Extern].

Integration To be able to compare the actual execution duration with the labor time of the employee properly, you have to implement BAdI /SCWM/EX_LM_BASICS_TIMEAVS in enhancement spot /SCWM/ES_LM_BASICS_TIMEAVS. The implementation must determine the labor time of the employee (processor) for the given evaluation interval. If you have connected an SAP ERP HR system (Rel. 4.6C or higher), and are using Personnel Time Management there, you can use enhancement implementation /SCWM/ESI_LM_BASICS_TIMEAVS to determine the labor time. If you want to transfer the performance document amount to a connected SAP ERP HRsystem Rel. 4.6C and higher as an external wage component, you must have already maintained the interface for External Wage Components in Customizing for the HR system.

Prerequisites ●

You have set up and activated Labor Management.

●

You have created indirect labor tasks [Seite 698] for effort times that are not recorded directly in the system.

●

To be able to draw conclusions for employee performance from the performance document, an executed workload must exist for every task associated with effort time.

●

You have implemented engineered labor standards [Seite 704] to enable you to compare planned and actual execution durations properly.

Performance-Document-Relevant Settings in the EWM System 1. Define the internal number range interval for the performance document in Customizing (IMG) for EWM, under Labor Management → Define Number Range for Performance Document. 2. Define the HR systems that are relevant for the employees in Customizing (IMG) for SCM Basis, under Master Data → Resource → Processor. If you have connected an SAP ERP HR system (Rel. 4.6C and higher), you have defined the corresponding logical system, number range interval for the performance document, and the version of the HR system. 3. To be able to forward the performance document amount to the SAP ERP HR system, you must enter the origin, which must match the ID of the application in the interface for External Wage Components in Customizing for the HR system. 4. You must also specify the wage types and currency that were permitted in the SAP ERP HR system for the interface when considering the application ID and the country grouping. 5. If you have not connected an HR system but still want to evaluate the performance of your employees, you must define a dummy system so that you can then assign a number range interval.

SAP Extended Warehouse Management (SAP EWM)

510

732

SAP Online Help

20.07.2007

Master Data Settings in SCM Basis You define the following fields in the processor master data: ●

You specify the HR system that is relevant for the employee in the business partner, under LM Attributes in the field HR Bus. System

●

If you have connected an SAP ERP HR system, you must also specify the personnel number of the employee on the Identification tab page.

●

Define a supply chain unit (SCU) for the Home Location under LM Attributes. This SCU must be the same as the SCU in which the processor is mainly active. The SCU defines the time zone for the evaluation intervals of the performance document.

Features You call the function from the SAP Easy Access screen, by choosing Extended Warehouse Management → Labor Management → Employee Performance → Employee Performance Overview. The performance overview lists the following: ●

Performance documents of the processor in the selected display interval

●

Cumulative, assigned, and executed workload data of the performance document

●

Dialog box allowing you to display the individual cumulative workload records

Processor in the Business Partner You create a performance document for a processor. In the master data for the business partner, you must have specified a HR system for the processor on the LM Attributes tab page, to determine a document number. If you have connected an SAP ERP HR system, you must also specify the personnel number of the employee on the Identification tab page. Define a supply chain unit (SCU) for the Home Location under LM Attributes. This SCU must be the same as the SCU in which the processor is mainly active. The SCU defines the time zone that the system uses to interpret the evaluation intervals for the employee's performance document.

Restriction When Changing the Performance Document The performance document contains the cumulative planned and actual execution durations of the assigned executed workload (EWL). The assignment of the EWL to the performance document is based on the processor and on the end of the execution date of the EWL, which lies within the evaluation interval of the performance document. If the evaluation interval of the performance document lies in the future, you cannot create any more additional EWLs. If the evaluation interval of the performance document does not lie in the future, or if the performance document has status Created, Deleted or Manually Deleted in display mode, this restriction does not apply. If a performance document has the status Created in change mode, or if it has the status For Approval, Transferred, Transferred Manually or To Delete, you cannot create an EWL and assign it to the performance document. If you still attempt to confirm an original document that generates an EWL that conflicts with an existing performance document time-wise, an error message is displayed. This restriction also applies if you change the EWL directly in the warehouse management monitor.

We recommend that you only create a performance document for evaluation intervals in the past. A performance document must only be given the status For

SAP Extended Warehouse Management (SAP EWM)

510

733

SAP Online Help

20.07.2007

Approval, if no further EWL falling within the evaluation interval of the performance document is going to be generated.

BAdI for Available Time To be able to compare the actual execution duration with the labor time properly, you have to implement BAdI /SCWM/EX_LM_BASICS_TIMEAVS in enhancement spot /SCWM/ES_LM_BASICS_TIMEAVS. The implementation must determine the labor time of the employee (processor) for the given evaluation interval. If you have connected an SAP ERP HR system (Rel. 4.6C or higher), and are using Personnel Time Management there, you can use enhancement implementation /SCWM/ESI_LM_BASICS_TIMEAVS to determine the labor time.

BAdI for Calculating the Amount If you want to calculate a performance-related amount for the performance document, you must implement BAdI /SCWM/EX_LM_BASICS_EPD_AMCALC in enhancement spot /SCWM/ES_LM_BASICS_EPD. The BAdI provides you with the information from the performance document and the assigned executed workload. You can also record or overwrite the amount in the performance document manually.

Authorization Concept You can use authorization object /SCMB/LMPD to record, change, display and delete performance documents. You can use the field Status when making changes to see whether this is possible in the current processing level, thereby realizing an approval process.

Check When creating a performance document for an employee, the system checks whether a gap in time or an overlap of the evaluation time period with existing performance documents exists. The system issues a warning.

Archiving You can archive performance documents using archiving object WME_EPD.

Activities ●

For the performance document to reflect the performance of an employee (processor) as precisely as possible, you must activate Labor Management for all process steps that bring about time effort for an employee.

●

If you are unable to record the time effort for processing a task when processing an original document, you must record the effort in an indirect labor task [Seite 698].

●

Depending on the system landscape, you can make the settings described under Integration. In an optimal integration setup, you can specify the labor time of an employee in a performance document from a time management system, and transfer a performance bonus to an HR system.

●

To enable a fair valuation of the employee performance, you must have implemented engineered labor standards [Seite 704], and have adjusted any storage parameters relevant for engineered labor standards that you have made changes to.

●

If you want to calculate a performance-related amount for the performance document, you must implement BAdI /SCWM/EX_LM_BASICS_EPD_AMCALC in enhancement spot /SCWM/ES_LM_BASICS_EPD. The BAdI provides you with the information from the performance document and the assigned executed workload. You can also record or overwrite the amount in the performance document manually.

SAP Extended Warehouse Management (SAP EWM)

510

734

SAP Online Help

20.07.2007

Example 1. In the middle of the current month, the group leader in the warehouse creates a performance document for each employee assigned to him or her, with the evaluation period of the last month. 2. The system reads the assigned EWL in the performance document for each employee. It copies the planned and actual execution durations into the performance document. The labor time of the employee is also displayed in the performance document, as the system reads the data from the time management system in the BAdI implementation for available time. 3. The group leader manually adjusts the time in the performance document of an employee, as this employee was not able to execute his tasks optimally due to a defect resource. 4. The group leader then calculates an amount for the newly created performance documents, enters the validity date of the performance document, selects a wage type for sending the information to an SAP HR system, and sets the status of the documents to For Approval. 5. The warehouse manager checks these new performance documents promptly, and sets their status to Approved. By starting the transmission program, the system transfers the amounts for all approved documents into the SAP HR system. In the HR system, the system considers these amounts as external wage components for payroll.

SAP Extended Warehouse Management (SAP EWM)

510

735

SAP Online Help

20.07.2007

Performance Document Definition A performance document enables you to perform an employee-related evaluation of the executed workloads (EWL) for a chosen time period. It contains the cumulative planned and actual execution durations of the assigned executed workload (EWL), and the labor time of the employee, and therefore enables you to draw conclusions about the performance or utilization of the employee. You create a performance document for a processor.

Integration The performance overview displays the following: ●

Multiple processors one after each other

●

Part of the processor’s master data

SAP Extended Warehouse Management (SAP EWM)

510

736

SAP Online Help

20.07.2007

Performance Document Status Use You use this function in the performance overview to change the status of performance documents. Resetting a status is only possible if you have not yet saved the document. In the figure, this is indicated by Cancel (transient). You can delete performance documents that have the status Created, For Approval and Approved. You can only set the statuses Transferred and Deleted by using the function Send Performance Document to HR (transaction /SCWM/EPD_TRANSFER). The figure below shows the changes that can be made to the status of a performance document.

Performance Document with Status

Created Set

Cancel For Approval

Set

Cancel Approved

Transfer program Transferred Set

Cancel To Delete

Transfer program

Cancel (transient)

Set

Manually Transferred Cancel (transient)

Set

Manually Deleted Deleted

Activities You call this function from the SAP Easy Access screen. Choose Extended Warehouse Management → Labor Management → Employee Performance → Employee Performance Overview.

SAP Extended Warehouse Management (SAP EWM)

510

737

SAP Online Help

20.07.2007

Performance Document and Connection to an HR System Use You can use this function to connect your performance documents [Extern] to an SAP HR system or to another, external HR system.

Features Performance Document with SAP HR If you have connected an SAP ERP HR system (Rel. 4.6C or higher), and are using Personnel Time Management there for your employees, you can use enhancement implementation /SCWM/ESI_LM_BASICS_TIMEAVS to determine the labor time of the processor. If you want to pay out a performance-related bonus, you must connect the SAP HR system (Rel. 4.6C or higher) to the EWM system, and transfer the performance document amount as an external wage component [Extern] of the employee to the HR system. If you want to undo the performance document transfer, you have to set the status of the performance document to To Delete, and send the document to the HR system again. This allows the system – if integration with payroll exists – to transfer the selected performance documents with status Approved or To Delete to the SAP HR system. The program log displays the performance documents for which the transfer was successful, or for which it was not possible. If the transfer was successful, the system changes the status of the performance document to Transferred or Deleted. The reference number of the generated external wage component (infotype 579) in the personnel master data of the employee is the document number of the transferred performance document.

Performance Document Without HR Connection If you use the performance document without a connection to an HR system, you can still use a customer implementation of BAdI /SCWM/EX_LM_BASICS_TIMEAVS for the available time of the processors to use other labor time information available in the system. If you do not want to use the data of the performance document or assigned workload to determine and pay out a performance-related bonus, you can still use the data to appraise the employee’s performance. If you want to pay out a performance-related bonus without using the advantages of a connection to an SAP HR system, you also do without the support of the system when transferring the amount to the responsible payroll, and when setting the status of the performance document to Transferred Manually. If you have revoked a bonus payment that was not supported by the system, you must set the status of the performance document to Deleted Manually.

Activities On the SAP Easy Access screen, choose Extended Warehouse Management → Labor Management → Employee Performance → Send Performance Document to HR.

SAP Extended Warehouse Management (SAP EWM)

510

738

SAP Online Help

20.07.2007

Analytical Functions Purpose This component provides you with analytical functions that make the shift from an administration-oriented to a strategically-oriented warehouse easier for you. Key figure functions and functions for graphical analysis, monitoring or control, enable you to analyze your warehouse. They help you to analyze and optimize the current warehouse situation. After analyzing the planned and current data, you can develop, implement, and monitor strategies to increase the efficiency of your warehouse. You can also continuously check the effects different scenarios have on your planning goals.

Implementation Considerations If you company uses BI Content for the data analysis, BI Content SAP NW 2004s BI Content Add-on 3 SP06 for Extended Warehouse Management (EWM) is available to you, under Supply Chain Management → Extended Warehouse Management → 0WM. In BI Content, you can create Queries through workbooks for strategic planning, or plan strategically. This is a planning example, with which you can use delivery items from the past to plan the required employees for each warehouse for the next two months. For more information, see SAP Library for SAP NetWeaver under SAP NetWeaver Library -> SAP NetWeaver by Key Capability -> Information Integration by Key Capability -> BI Content -> Supply Chain Management -> Extended Warehouse Management → Queries. If you use BI Content, you extract data from the EWM system into BI Content by using DataSources. You make the settings required for this in Customizing for the source system. You have to: ●

Copy the DataSources and postprocess them where necessary

●

Configure the posting mode

●

Activate the BI update

For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Interfaces → SAP Business Information Warehouse → Business Content DataSources or → General Settings. If you are using the Warehouse Cockpit as an example implementation of the Easy Graphics Framework (EGF) and want to enhance it, make the required settings in the Easy Graphics Framework. For more information, see Easy Graphics Framework [Seite 68].

Features EWM System In EWM, you can use the following areas and functions with BI Content: ●

Customizing (copy and postprocess DataSources, configure posting mode, activate BI update, make settings for the Easy Graphics Framework, measurement services, make settings that are Labor-Management-relevant for operational planning and simulation)

●

Master data processing (create processor, create formulas and conditions)

●

Operational planning and simulation (create planning formulas, configure preprocessing)

SAP Extended Warehouse Management (SAP EWM)

510

739

SAP Online Help

20.07.2007

●

You can use the measurement services to record your warehouse key figures and have the system define them automatically.

●

In the Warehouse Cockpit [Seite 741], you can display the measurement services graphically, enabling you to monitor your warehouse key figures visually. You can also run the measurement services in the background, using a report. You can then write the results to the database. You can specify a lower and upper limit value for each measurement service. If this value is then exceeded or fallen short, an exception that you have specified can be triggered. You can evaluate these exceptions in the warehouse management monitor. The exceptions can be used for automated follow-on actions, such as notifications.

●

There are also other evaluation options available to you in the warehouse management monitor [Seite 878]. You can use the nodes Labor Utilization and Executed Workload to analyze the efficiency of your employees, for example.

BI Content BI Content is another option that you can use to analyze your data. Here you can extract data from the EWM system using the following DataSources: ●

Executed workload (0WM_EWL)

●

Warehouse task (0WM_WT_WO)

●

Warehouse orders (0WM_WO)

●

Value-added services (0WM_VAS)

●

Delivery-item-related execution data (0WM_PL_DLVI)

●

Measurement service descriptions (0WM_MS_TEXT)

●

Measurement service results (0WM_MS_RESULT)

●

Exception code (0WM_EXCODE)

●

Delivery items (0WM_DLVI)

●

Storage bins (0WM_BIN)

You can use the extracted data to create Queries, and plan strategically.

SAP Extended Warehouse Management (SAP EWM)

510

740

SAP Online Help

20.07.2007

Warehouse Cockpit Purpose You can use the Warehouse Cockpit to display your warehouse key figures and defined Easy Graphics Framework objects (EGF objects) graphically, and to evaluate or monitor them using defined chart types. It enhances text-based SAP solutions, and was developed to be implemented in a strategically oriented warehouse. It supports new processes, such as working with analytical functions when managing a warehouse using Extended Warehouse Management (EWM). The Warehouse Cockpit displays the measurement services [Seite 744] delivered by SAP and created by you. It is an example implementation of the Easy Graphics Framework (EGF) [Seite 68], delivered by SAP, which contains overdue objects and objects of the material flow system [Seite 820] (MFS). You can display the utilization and resource situation of your warehouse using the objects you have defined. The figure shows the EGF objects bars, stacks, speedometer and time for the example for open physical inventory documents.

Implementation Considerations If your firm wants to implement the Warehouse Cockpit, and the objects or chart types delivered in the example implementation are not enough for you, you must use the Easy Graphics Framework (EGF) in Customizing for EWM to extend the EGF settings and define additional objects or chart types. For more information about the Easy Graphics Framework, see Easy Graphics Framework [Seite 68].

Features ●

The system displays newly created measurement services in the Warehouse Cockpit automatically. You must include the measurement services in the menu tree by

SAP Extended Warehouse Management (SAP EWM)

510

741

SAP Online Help

20.07.2007

choosing Show Hidden Objects. You can then use Drag&Drop to move the measurement service to the corresponding folder Measurement Service. ●

If you display a measurement service either by double-clicking it or via the menu, it is redefined after intervals that are specified in the refresh rate [Seite 76].

●

If the threshold values defined in the measurement services are exceeded or fallen short, the system triggers an exception. You define exceptions in Customizing for EWM. For more information, see the Implementation Guide (IMG) for EWM under CrossProcess Settings → Exception Handling → Define Exception Codes.

The delivered Warehouse Cockpit contains the following EGF objects: ●

Measurement services

●

Material flow system (MFS)

●

○

Status of communication channel

○

Status of communication layer

○

Status of process for telegram repetition

○

Status of MFS resource

Overdue objects ○

Overdue warehouse tasks

○

Overdue warehouse orders

○

Overdue waves

○

Warehouse tasks time series

○

Warehouse orders time series

The following chart types are available for the measurement services: ●

Bars

●

Stacks

●

Time

●

Speedometer

●

Table

The following chart types are available for the objects of the material flow system: ●

Traffic light

●

Table

The following chart types are available for overdue objects: ●

Bars

●

Stacks

SAP Extended Warehouse Management (SAP EWM)

510

742

SAP Online Help ●

Time

●

Table

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

743

SAP Online Help

20.07.2007

Measurement Services Use You use this function to define your own warehouse key figures supported by the system. You map your key figures using tailored and calculated measurement services (TMS and CMS). You start these using the program Start Measurement Services, which you can schedule to run regularly. Examples of warehouse key figures include: ●

Outbound deliveries that have left the warehouse too late

●

Number of open physical inventory documents that are older than 5 days old

●

Number of handling units in goods receipt

These warehouse key figures can be called at any time, and represent tools which the warehouse manager can use to check and plan his warehouse more effectively. He does not have to track his warehouse key figures constantly on the screen, instead he can trigger alerts if certain values are exceeded or fallen short. Measurement services are output in the base unit of measure of the warehouse.

Integration The determined key figures are used in the following functions: ●

Warehouse management monitor, for creating a tailored measurement service (TMS) under certain conditions

●

Operational planning [Seite 728] in Labor Management and for calculating engineered labor standards [Seite 704]

●

Warehouse Cockpit [Seite 741], to monitor the results graphically

●

BI Content of Extended Warehouse Management (0WM)

Features Measurement services are based on one another: ●

A tailored measurement service (TMS) is based on a basic measurement service (BMS) selected by you. BMSs are the building blocks of your warehouse key figures, and cannot be uses on their own. You can split these up into BMS groups, according to your business requirements. A BMS is a query to a business object, which the system executes without the user having to make an entry. Examples of BMSs are number of inbound deliveries, or number of warehouse tasks.

●

A calculated measurement service (CMS) is a mathematic formula. It consists of: ○

One or more CMSs

○

One or more TMSs

○

A mathematic function

SAP Extended Warehouse Management (SAP EWM)

510

744

SAP Online Help

20.07.2007

You define the measurement services on the SAP Easy Access screen, by choosing Extended Warehouse Management → Settings → Measurement Services, or in Customizing for EWM under Monitoring → Measurement Services. For each key figure you can do the following: ●

Define upper and lower threshold values

●

Define exception codes if these values are exceeded or fallen short

●

Trigger a workflow based on exception codes, such as creating a warehouse task

●

Trigger an alert based on exception codes, such as sending a message

Activities 1. SAP delivery BMS groups and individual BMSs. If you want to add more groups or BMSs, in Customizing for EWM, choose Monitoring → Measurement Service → Define Basic Measurement Service Group or Define Basic Measurement Service (BMS). If you want to define your own BMS, enter a function module that you have created for the selection screen and selection. 2. You can choose to create a TMS and CMS using a view or a wizard. On the SAP Easy Access screen, choose Extended Warehouse Management → Settings → Measurement Services, or in Customizing for EWM choose Monitoring → Measurement Services. 3. You schedule and plan the measurement services regularly using program Start Measurement Services. ...

Example A warehouse manager wants to know each morning how many warehouse orders a processor has executed the previous day. For this he makes the following settings: ...

1. He starts by defining a TMS based on the BMS he requires. He selects BMS 1 “Number of Warehouse Orders“ and BMS 2 ”Number of Processors“. 2. He then adjusts these to match his requirements, by creating selection variants 1 and 2. 3. He creates CMS 1 in the formula editor in such a away that TMS 1 is divided by TMS 2. As a result, he is given the number of warehouse orders per processor, for example 40 warehouse orders per processor. The figure below shows how the individual measurement services are based on one another.

SAP Extended Warehouse Management (SAP EWM)

510

745

SAP Online Help

20.07.2007

Variant 1: Status = Completed

BMS 1: TMS 1

No. of warehouse orders

CMS 1 = TMS 1/TMS 2

Variant 2: Date = Yesterday

BMS 2: No. of processors

40 warehouse orders per processor

TMS 2

SAP Extended Warehouse Management (SAP EWM)

510

746

SAP Online Help

20.07.2007

Tailored Measurement Service (TMS) Use You use this function to build warehouse key figures, which you can use to check the effectiveness of your warehouse. You select a basic measurement service (BMS) on which your TMS is to be based, and adjust it to fit your business requirements. You add special selection criteria to the BMS, such as the activity area, by creating a selection variant. The result is a key figure in the base unit of measure of the warehouse.

Features You define a TMS on the SAP Easy Access screen, by choosing Extended Warehouse Management → Settings → Measurement Services, or in Customizing for EWM under Monitoring → Measurement Services. Both options allow you to either use a wizard to define a TMS, or to define one in a view.

If you create a TMS using Customizing, it will be included in a transport request, meaning that you can use in other systems and not just locally. If you create a TMS using the SAP Easy Access screen, you can only use it locally. You can do the following: ●

Create, copy, change, or delete a TMS

●

Create, change, or delete variants for the BMSs

●

Define threshold values, exceptions, and minimum repeat intervals

●

Test the TMS

Example The number of warehouse orders with status Completed.

SAP Extended Warehouse Management (SAP EWM)

510

747

SAP Online Help

20.07.2007

Calculated Measurement Service (CMS) Use You use this function to build the warehouse key figures that are used to check the effectiveness of your warehouse. You can use a formula editor to connect multiple tailored measurement services (TMS) in a complex formula, to determine the performance of your employees, for example. You create the formula in the formula editor [Seite 694], and for one part of the formula you choose a tailored measurement service (TMS), another calculated measurement service (CMS), or a mathematical function. As a result, the TMS returns a key figure in the base unit of measure of your warehouse.

Prerequisites You have defined one or more TMSs on which the CMS is to be based.

Features You define a CMS on the SAP Easy Access screen, by choosing Extended Warehouse Management → Settings → Measurement Services, or in Customizing for EWM under Monitoring → Measurement Services. Both options allow you to either use a wizard to define a CMS, or to define one in a view.

If you create a CMS using Customizing, it will be included in a transport request, meaning that you can use in other systems and not just locally. If you create a CMS using the SAP Easy Access screen, you can only use it locally. You can do the following: ●

Create, copy, change, or delete a CMS

●

Define threshold values, exceptions, and minimum repeat intervals

●

Test the CSM and check the correctness of the formula

Example Key figure that specifies the number of warehouse orders per processor. Here, CMS 1 (number of warehouse orders with status Completed) is divided by CMS 2 (number of processors with yesterday’s date).

SAP Extended Warehouse Management (SAP EWM)

510

748

SAP Online Help

20.07.2007

Evaluation of Measurement Services Use You use this function to evaluate the defined measurement services.

Features Start Measurement Services You use this program to start the tailored and/or calculated measurement service. By selecting certain selection criteria, you have a “background agent“ available, which you can use to monitor the history of particular warehouse key figures, if you schedule the report regularly. You save the results in the following: ●

Database

●

Local file

●

Logical file

Here you also configure whether the measurement services trigger an exception code if defined threshold values are exceeded or if a shortfall arises.

Delete Measurement Service Results You can use this program to delete the results of the tailored and calculated measurement services from the database, thereby preventing the database tables from becoming too large.

Activities You start the measurement services from the SAP Easy Access screen, under Extended Warehouse Management → Settings → Measurement Services → Periodic Processing.

SAP Extended Warehouse Management (SAP EWM)

510

749

SAP Online Help

20.07.2007

Resource Management Use Resource management maximizes the efficiency of warehouse processes by: Facilitating the management and distribution of work via queues [Seite 764] ●

Enabling the execution of work by resources in a radio frequency (RF) and non-RF environment

Optimizing the selection of warehouse orders for resources [Seite 752] requesting work ●

Enabling effective monitoring and controlling of resources

Features Controlled Distribution of Work via Queues The assignment of resources to queues enables focused management and distribution of work in the warehouse. For more information, see Queue. Warehouse Order Execution in RF and Non-RF Environments Resources can execute work via RF and non-RF transactions. For more information about RF transactions, see Standard RF Functions [Seite 789]. Manual and Automatic Assignment of Warehouse Orders to Resources Warehouse orders (WOs) can either be manually assigned to a resource by a warehouse manager, or automatically assigned by the system. For more information, see Assignment of Warehouse Order to Resource [Seite 755]. Optimized Warehouse Order Selection Resources that require system-guided work are offered the most appropriate WOs. Here a number of factors are taken into consideration, for example, the mode, latest start date (LSD), execution priorities, assigned queues, qualification of resource type, and WO status. For more information, see Warehouse Order Selection [Seite 757]. Resource Controlling and Monitoring Warehouse managers can use the warehouse management monitor [Seite 878] to do the following: ●

Analyze resource workload

●

Monitor WO execution by resources

●

Send messages to resources

●

Logon and logoff resources

●

Assign resource groups to queues and remove this assignment

●

Create and maintain users and resources

●

Change the queue of a WO

●

Change the LSD of a WO

For more information, see Monitor Methods [Seite 882]. SAP Extended Warehouse Management (SAP EWM)

510

750

SAP Online Help

20.07.2007

See also: Resource Management Using Radio Frequency [Seite 814].

SAP Extended Warehouse Management (SAP EWM)

510

751

SAP Online Help

20.07.2007

Resource Definition A resource is an entity representing a user or equipment, which can execute work in the warehouse.

Use A resource can log on to a radio frequency (RF) or non-RF environment. Once the resource is logged on to the system, it can receive work for execution, and can be tracked and displayed in the warehouse management monitor [Seite 878].

For more information about logging on to an RF environment, see Logon [Seite 790]. For more information about how resources receive work, see Assignment of Warehouse Order to Resource [Seite 755].

Structure A resource belongs to a resource type [Seite 753] and resource group [Seite 754].

You define a resource in the transaction for resource maintenance. To do so on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Resource Management → /SCWM/RSRC – Maintain Resource. Alternatively you can define a resource by using the warehouse management monitor (method [Seite 882] Maint. Resource).

SAP Extended Warehouse Management (SAP EWM)

510

752

SAP Online Help

20.07.2007

Resource Type Definition A resource type is a grouping of resources with similar technical or physical qualifications.

Use The resource type determines the following for its corresponding resources [Seite 752]: ●

Horizontal velocity The velocity of a resource can influence the LSD of a warehouse order (WO). For more information, see Latest Starting Date (LSD) [Seite 760].

●

Applicability of position management For more information, see Position Management [Seite 795].

●

Qualifications and preferences (reflected by priority values) regarding bin access types [Extern] and HU type groups [Extern] The qualifications and priority values influence which WOs are selected for a resource requesting work. For more information, see Warehouse Order Selection [Seite 757].

You define resource types, and assign to them qualifications, in Customizing for Extended Warehouse Management → Cross-Process Settings → Resource Management → Define Resource Types. You maintain the qualification priority values using the execution priority maintenance transaction, accessed on the SAP Easy Access screen (Extended Warehouse Management → Master Data → Resource Management → /SCWM/EXECPR - Maintain Execution Priorities).

SAP Extended Warehouse Management (SAP EWM)

510

753

SAP Online Help

20.07.2007

Resource Group Definition A resource group is a grouping of resources for queue [Seite 764] assignment purposes.

Use The resource group determines the sequence of allowed queues for its corresponding resources [Seite 752], which can influence which WOs are selected for a resource. For more information, see Warehouse Order Selection [Seite 757].

You assign/unassign a resource group to/from a queue using the queue sequence for resource group transaction, accessed on the SAP Easy Access screen (Extended Warehouse Management → Master Data → Resource Management → /SCWM/QSEQ - Maintain Queue Sequence for Resource Group), or from the warehouse management monitor [Seite 878] (Assign Queue/Unassign Queue methods [Seite 882]).

SAP Extended Warehouse Management (SAP EWM)

510

754

SAP Online Help

20.07.2007

Assignment of Warehouse Order to Resource Purpose Warehouse orders (WOs) can be assigned to resources [Seite 752] in radio frequency (RF) and non-RF environments. In an RF environment, WOs can be assigned manually or automatically, while in a non-RF environment, WOs are only manually assigned.

Prerequisites In the case of automatic WO assignment to a resource, the WOs must belong to a queue [Seite 764] to which the resource is assigned, and which the resource is authorized to work in.

Process Warehouse Order Assignment to a Resource Non-RF Environment

RF Environment

1 .

A resource logs on to the desktop environment.

A resource logs on [Seite 790] to the RF environment.

2 .

The warehouse manager assigns the WO to the resource via the Assign Rsrce monitor method [Seite 882].

One of the following occurs:

3 .

●

The warehouse manager prints out the WO and gives it to the resource.

The warehouse manager assigns a WO to the resource via the Assign Rsrce warehouse management monitor method.

Any available WOs can be manually assigned to a resource, including those from queues to which the resource is not assigned. ●

The resource requests work by choosing a system-guided option from the RF menu.

In such a case, the system assigns to the resource the most appropriate WO. For more information, see Warehouse Order Selection [Seite 757]. ●

The resource requests work by choosing a manual option from the RF menu (for example, Pick by HU). In such a case, the system assigns to the resource the specific WO.

You can also ensure that a new WO is automatically

SAP Extended Warehouse Management (SAP EWM)

510

755

SAP Online Help

20.07.2007 assigned to a resource after confirmation of a WO. You define this in Customizing for Extended Warehouse Management under Mobile Data Entry → Radio Frequency (RF) Framework → Define Logical Transaction Flow.

SAP Extended Warehouse Management (SAP EWM)

510

756

SAP Online Help

20.07.2007

Warehouse Order Selection Purpose When a resource [Seite 752] chooses a system-guided RF transaction, the system finds for the resource the most appropriate warehouse order (WO).

Process ...

1. A resource requests work via a system-guided RF transaction. The system checks for available WOs that are manually assigned to the resource by the warehouse manager. For more information about manual assignment, see Assignment of Warehouse Order to Resource [Seite 755]. If the resource chose a System-Guided by Queue option, the WOs must also belong to the selected queue [Seite 764]. a. If a WO belongs to a queue, the queue’s operating environment must be consistent with that of the resource. b. If more than one WO is assigned to the resource, the list of possible WOs for selection is sorted in the following order: i.

WOs belonging to the resource’s assigned queue

WOs belonging to the resource group’s [Seite 754] assigned queues, according to the defined queue sequence. ii.

WOs that do not belong to any queue

c. If more than one WO falls within any of these queue classifications, the WOs are sorted as follows: In ascending order, by latest starting date (LSD) [Seite 760] i.

In descending order, by execution priority.

For more information, see Warehouse Order Prioritization [Seite 761]. 2. If there are no manually assigned WOs, the system checks for available WOs. a. The WOs must comply with the following conditions: i.

The WOs belong to one of the resource’s or resource group’s assigned queues.

ii.

The WOs belong to queues in which the resource is authorized to work.

iii.

The WOs belong to queues with the same operating environment as the resource.

iv.

If the resource chose a System-Guided by Queue option, the WOs must also belong to the selected queue.

The WOs can be executed by the requesting resource type (according to its bin access type [Extern] and handling unit type group [Extern] qualifications). b. The WOs are sorted as follows: i.

In ascending order, by latest starting date (LSD)

ii.

In descending order, by execution priority.

SAP Extended Warehouse Management (SAP EWM)

510

757

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

758

SAP Online Help

20.07.2007

Mode Definition A mode is a state that determines the following: ●

Weighting factors used for warehouse order prioritization [Seite 761]

●

Time intervals and units of measure for rounding latest starting dates (LSDs) [Seite 760]

Use When a warehouse task (WT) is grouped into a warehouse order (WO), its mode is set as: ●

The mode assigned to the corresponding wave [Seite 769], if applicable.

You can assign a mode to a wave in one of the following ways:

●

●

By defining the mode in the wave template [Seite 767] (to do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Wave Management → /SCWM/WAVETMP – Maintain Wave Templates)

●

By defining the mode in a wave directly (to do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Wave Management → /SCWM/WAVE – Maintain Wave)

The mode assigned to the following determination criteria: ○

Warehouse

○

Activities associated with the WTs

You define modes and their determination criteria in Customizing for Extended Warehouse Management → Cross-Process Settings → Resource Management → Define Modes. The mode is then used to calculate the LSDs and priorities of the WTs. When determining the LSD of the warehouse order containing the WTs, the system uses the rounding time interval of the mode of the first WT in the WT sequence.

SAP Extended Warehouse Management (SAP EWM)

510

759

SAP Online Help

20.07.2007

Latest Starting Date (LSD) Definition The latest starting date (LSD) is the latest time by which execution of a warehouse order (WO) should commence, so that it is completed by the due date. The LSD for each warehouse task (WT) of a WO is calculated as follows: LSD = WO due date - (planned execution duration + planned movements duration) ●

The due date is taken from one of the following: ○

The picking completion date in the WT

○

If there is no picking completion date in the WT, the planned goods issue date in the warehouse request (WR) [Extern]

●

The planned execution duration is taken from the WO

●

The planned movements duration is equal to distance/velocity. The following rules apply here: ○

Distance is calculated according to the bins’ coordinates, using the manhattan metric

Velocity is the lowest horizontal velocity from all resource types [Seite 753] that are qualified to execute the WT

Use The system calculates the LSD of a WO by: ...

1. Calculating the LSD of each WT as described above 2. Taking the worst-case scenario LSD (that is, the earliest LSD) Rounding down this LSD according to the rounding time interval of the relevant mode [Seite 759] (that is, the mode of the first WT in the WT sequence) The LSD is one of the factors that influence WO selection. For more information, see Warehouse Order Selection [Seite 757].

SAP Extended Warehouse Management (SAP EWM)

510

760

SAP Online Help

20.07.2007

Warehouse Order Prioritization Use Warehouse order (WO) prioritization ensures that the system selects for a resource [Seite 752] the WO that is most suitable for it.

Prerequisites You have assigned bin access types [Extern] and handling unit type groups [Extern] to resource types [Seite 753] in Customizing for Extended Warehouse Management → CrossProcess Settings → Resource Management ### Define Resource Types.

Activities ...

1. You maintain the following using the execution priority maintenance transaction (on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Resource Management → /SCWM/EXECPR - Maintain Execution Priorities): ○

Bin access type (BAT) and handling unit type group (HUTG) priorities per resource type (a value from 1-10) The priority values reflect the preferences of a resource type to work in a particular bin access type, or with a HU type group.

○

Warehouse process category (WPC) priority (a value from 1-10)

Priority weightings per mode [Seite 759] (a value from 1-100). The weighting of a priority parameter reflects the relative importance of the parameter in determining the total priority of a warehouse task (WT). The weightings may vary according to activity, which is reflected by the mode.

If you do not maintain a BAT or HUTG priority value for a particular resource type, the resource type is not qualified to work in the bin access type or with the HU type group. 2. When a WT is combined into a WO, it is assigned a total priority, calculated as follows: Priority = (BAT Weighting/100 x BAT Priority Value) + (HUTG Weighting/100 x HUTG Priority Value) + (WPC Weighting/100 x WPC Priority Value)

The weightings are based on the mode of the first WT in the WT sequence. 3. The total priority of the WO is set from the highest priority of its constituent WTs.

Example In the following example, we assume that the warehouse process category for all WTs is the same, and therefore ignore the warehouse process category priorities. You maintain the following execution priorities for resource type A:

SAP Extended Warehouse Management (SAP EWM)

510

761

SAP Online Help

20.07.2007

Bin Access Type Priorities Bin Access Type

Priority

BAT1

6

BAT2

8

BAT3

4

Handling Unit Type Group Priorities HU Type Group

Priority

HUTG1

5

HUTG2

3

HUTG3

9

You also maintain the following mode priority weightings: Mode Priority Weightings Mode

Priority Parameter

Weighting

1

Bin Access Type

45

1

HU Type Group

30

1

Process Type

15

2

Bin Access Type

30

2

HU Type Group

50

2

Process Type

10

Resource A is currently assigned to queue 5, to which the following WOs are assigned: WO 4432 Warehouse Task

Mode

Bin Access Type

HU Type Group

LB 342

1

BAT3

HUTG3

LB 355

2

BAT2

HUTG1

Warehouse Task

Mode

Bin Access Type

HU Type Group

LB 364

2

BAT1

HUTG2

LB 340

1

BAT2

HUTG3

WO 4435

The priority values for resource A are calculated as follows: WO 4432 Priority (WT 342) = (0,45*4) + (0,3*9) = 1,8+ 2,7 =4,5

SAP Extended Warehouse Management (SAP EWM)

510

762

SAP Online Help

20.07.2007

Priority (WT 355) = (0,3*8) + (0,5*5) = 2,4 + 2,5 = 4,9

Total priority of WO 4432 = 4.9

WO 4435 Priority (WT 364) = (0,3*6) + (0,5*3) = 1,8 + 1,5 = 3,3

Priority (WT 340) = (0,45*8) + (0,3*9) = 3,6 + 2,7 = 6,3

Total priority of WO 4435 = 6.3

SAP Extended Warehouse Management (SAP EWM)

510

763

SAP Online Help

20.07.2007

Queue Definition A queue is a logical file to which warehouse tasks (WTs) for processing are assigned. Queues define movements by which work in the warehouse is managed and assigned.

Use The management and distribution of work in the warehouse is accomplished by the assignment of resources [Seite 752] and WOs to queues. A resource may execute only those WOs that belong to one of its allowed queues (unless the WOs are manually assigned). This means a queue to which the resource or resource group is assigned, and in which the resource is authorized to work. In addition, a resource working within a particular operating environment may execute only those WOs that belong to a queue in the same operating environment.

You determine the operating environment of a queue during queue definition (Customizing for Extended Warehouse Management → Cross-Process Settings → Resource Management → Define Queues). The operating environment of a resource is determined when the resource logs on to the RF [Seite 790] or non-RF environment. Resource Assignment to Queue You can assign a resource to a specific queue, or assign its resource group [Seite 754] to a sequence of allowed queues. WO selection will be performed first according to the resource’s assigned queue, and, in the absence of an assigned queue, according to the resource group’s queue sequence. For more information, see Warehouse Order Selection [Seite 757].

You assign a resource to a queue using the resource maintenance transaction, accessed on the SAP Easy Access screen (Extended Warehouse Management → Master Data → Resource Management → /SCWM/RSRC - Maintain Resource), or from the warehouse management monitor [Seite 878] (Maint. Resource method [Seite 882]). You assign/unassign a resource group to/from a queue using the queue sequence for resource group transaction, accessed on the SAP Easy Access screen (Extended Warehouse Management → Master Data → Resource Management → /SCWM/QSEQ - Maintain Queue Sequence for Resource Group), or from the warehouse management monitor (Assign Queue/Unassign Queue methods) Warehouse Order Assignment to Queue When the system creates a WT, it searches for an appropriate queue to assign to it, based on the following WT parameters: ●

Source activity area

●

Destination activity area

●

Bin access type [Extern]

●

Warehouse process type

SAP Extended Warehouse Management (SAP EWM)

510

764

SAP Online Help

20.07.2007

The search is performed in accordance with the access sequence, with the initial search being for an entry with all of these parameter values. If no queue is found, the queue determination table is read again, according to the next entry in the sequence.

You define queue determination criteria and access sequences in Customizing for Extended Warehouse Management → Cross-Process Settings → Resource Management → Define Queues.

SAP Extended Warehouse Management (SAP EWM)

510

765

SAP Online Help

20.07.2007

Wave Management Use You can use Extended Warehouse Management (EWM) to combine items or split items from warehouse requests [Extern] for outbound deliveries into waves [Seite 769]. These waves must be picked and processed at roughly the same time.

Features You can use wave templates [Seite 767] for both automatic and manual wave generation. You can process waves [Seite 771]. You can use automatic wave assignment [Seite 773].

SAP Extended Warehouse Management (SAP EWM)

510

766

SAP Online Help

20.07.2007

Wave Template Definition Schema that defines the attributes of all the waves [Seite 769] that are based on it.

Use Wave templates serve as the infrastructure for automatic wave assignment [Seite 773]. They enable the same wave attributes to be reused for different warehouse request items [Extern] that comply with the same conditions. You can also use wave templates to manually create waves, or, in the case of automatic wave assignment, to assign items or split items from the warehouse requests to existing waves that are based on the wave templates.

You define wave templates using the transaction for maintaining wave templates. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Wave Management → /SCWM/WAVETMP – Maintain Wave Templates.

Structure A wave template may consist of one or more wave template options.

Wave Template Attributes The following attributes are available for wave templates: ●

Release method with the possible values Automatic, Immediate, and Manual For more information, see Processing of Waves [Seite 771].

●

Wave type that enables specific monitoring in the warehouse management monitor [Seite 878]

●

Wave category that you can use as a filter for warehouse order creation rules For more information, see the Implementation Guide (IMG) for Extended Warehouse Management under Cross-Process Settings → Warehouse Order → Define Filters for Warehouse Order Creation Rules.

●

Wave Assignment Also Possible After Wave Release indicator that you can use to assign additional warehouse request items to a wave that has already been released

●

Control for bin denial You can choose between the following: ○

You can leave an item in a wave, in other words, release it again later.

○

You can remove an item from a wave, in other words, reassign the item.

○

You can have the system immediately create a warehouse task with an alternative source bin.

Wave Template Option Attributes The following attributes are available for wave templates options: ●

Data for date and time:

SAP Extended Warehouse Management (SAP EWM)

510

767

SAP Online Help

20.07.2007

○

Lock time, in other words, the time up to which you can add items to the wave.

○

The number of days before the wave completion date that is used to define the lock date (lock days).

○

Release time, in other words, the time by which the wave must be released.

○

The number of days before the wave completion date that is used to define the release date (release days).

○

Picking completion time, in other words, the time by which you must have completed picking for the wave.

○

The number of days before the wave completion date that is used to define the picking completion date (pick completion days).

○

Packing completion time, in other words, the time by which you must have completed packing for the wave.

○

The number of days before the wave completion date that is used to define the packing completion date (packing completion days).

○

Staging completion time, in other words, the time by which you must have completed material staging for the wave.

○

The number of days before the wave completion date that is used to define the staging completion date (staging completion days).

○

Wave completion time, in other words, the time when the completion of all processing operations for the wave is planned.

●

Calendar for defining workdays

●

Staging area group for the resulting warehouse tasks (WTs)

●

Staging area for the resulting WTs

●

Indicator for special activity that determines another activity. You can use this activity to change the activity category that is defined by the warehouse request. All WTs created when the wave is released receive the new activity (and thus the corresponding activity area and pick path).

●

Mode [Seite 759] that applies to all WTs created when the wave is released

●

Capacity profile for defining capacity limits

SAP Extended Warehouse Management (SAP EWM)

510

768

SAP Online Help

20.07.2007

Wave Definition Grouping of warehouse request items [Extern] to control warehouse activities, for example, picking, or posting changes. These groupings are then processed together in subsequent processes, for example, the transfer of all warehouse request items assigned to a wave at a certain point in time to warehouse task creation. The warehouse task items created are then forwarded to warehouse task creation.

Use Extended Warehouse Management (EWM) can combine warehouse request items and split items into waves on the basis of criteria such as activity area, route, or product. Waves can be created automatically or manually using existing wave templates [Seite 767]. If you want to manually create a wave, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Wave Management → /SCWM/WAVE Maintain Waves and then choose Create. EWM creates an empty wave. You must manually enter the remaining information, for example, the assignment of warehouse request items. For more information, see Processing of Waves [Seite 771].

Example Example of Grouping Warehouse Request Items The following figure shows how EWM combines items from different warehouse requests with different routes and picking areas into waves. EWM combines the items WR Item 10 and WR Item 20 from warehouse request 100 and the item WR Item 10 from warehouse request 20 into wave 1on the basis of route A.

WR 100 WR Item 10 WR Item 20 WR Item 30

Route A

Wave 1

WR 200 WR Item 10 WR Item 20 WR Item 30 WR Item 40

Route B

WR 300 WR Item 10

Wave 2

Wave 3

Route C

SAP Extended Warehouse Management (SAP EWM)

510

769

SAP Online Help

20.07.2007

Assignment of an Item to Different Waves The following figure shows how EWM assigns a warehouse request item with different partial quantities to different waves if rough picking location determination results in different items due to a quantity-dependent picking strategy. In rough picking location determination, EWM assigns warehouse request item 10 with a quantity of 111 of product A to three different picking areas in accordance with the quantitydependent picking strategy. One piece is assigned to picking area PA1, ten pieces are assigned to picking area PA2, and 100 pieces are assigned to picking area PA3.

WR Header: 100 WPT: 601

Rough Location Determination

Route: 77

Product

Picking Area

WR Item: 10

Quantity

A

PA1

1

Product

Quantity

UoM

A

PA2

10

A

111

Unit

A

PA3

100

WR 100

WR Item 10 Quantity 111 Units

PA3 100

Wave 1 (PA3)

PA2 10

PA1 1

Wave 2 (PA2)

SAP Extended Warehouse Management (SAP EWM)

Wave 3 (PA1)

510

770

SAP Online Help

20.07.2007

Processing of Waves Use You can process waves and thereby control your warehouse activities.

Prerequisites You have defined number ranges for waves. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Master Data → Define Number Ranges. If you want EWM to save the logs for the wave, you have created an entry for the warehouse and the subobject WAVE (wave processing) as well an entry for the warehouse and the subobject WAVE_REL (wave release). For example, you can define that you want to see all messages in the application log with the status Additional Information. You have made these settings on the SAP Easy Access screen under Extended Warehouse Management → Settings → Activate Application Log.

Features You can process waves in the following ways: ●

Lock or unlock You can lock a wave with the status I (initial). As a result, the status of the wave becomes H (Locked). When you unlock a wave, EWM resets the status of the wave to I. You cannot release locked waves.

●

Merge You can merge as many waves as you want. The prerequisites are: ○

The waves have not yet been released, in other words, they have the status I (initial, wave is created) or H (hold, wave is locked).

○

All the waves have the same status, either I or H.

EWM assigns warehouse request items to the waves. When you merge waves, EWM assigns all the warehouse request items for the selected waves to the first wave selected. EWM always uses the name of the top row. For example, you have waves 123, 456 and 789. If you select and merge these, EWM merges these 3 waves into wave 123. ●

Release Waves are used to create warehouse orders and warehouse tasks. They can be released in the following ways: ○

Automatically EWM creates a job that automatically releases waves on the release day and at the release time.

○

Immediately When you or EWM create a wave, EWM releases this wave immediately.

○

Manually You can manually release a wave at any point in time in the monitor or in wave processing.

SAP Extended Warehouse Management (SAP EWM)

510

771

SAP Online Help

20.07.2007

When you manually release waves, you can also release locked waves. In this case, EWM sets the status Locked for the warehouse orders created. As a result, these warehouse orders [Seite 419] are locked for further processing for the time being. When you or EWM release a wave to generate warehouse tasks, EWM copies the staging area and the mode of the wave to warehouse task. You can release waves multiple times. For example, if you release a wave, but EWM can only generate some of the required warehouse tasks since there is not enough stock, you can release the wave again at a later point in time. You can display the log by using the Release Log button. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Wave Management → Maintain Waves. ●

Subsystem You can release a wave for a downstream subsystem. As a result, EWM transfers the warehouse orders to the downstream subsystem.

●

Assign or remove assignment You can assign warehouse request items to a wave or remove the assignment. Here, the lock time for the wave must not have expired yet. Moreover, the wave must not have been released yet. If you have set the Wave Assignment Also Possible After Wave Release indicator as an attribute in the wave template, you can, however, assign an additional warehouse request item to waves that have already been released.

●

Split You can select a warehouse request item and remove it from the current wave. EWM creates a copy of the wave and assigns the warehouse request item to the copy.

●

Assign automatically EWM automatically assigns the chosen warehouse request items to waves. To do this, the system uses the same logic as for the automatic wave assignment [Seite 773].

●

Delete When EWM deletes a wave, it removes the assignment of all the warehouse request items to the wave. EWM deletes a wave completely, in other words, you can no longer archive it.

Activities If you want to perform the activities described above, you work with either the monitor (transaction /SCWM/MON) or with wave processing. For wave processing, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Wave Management → /SCWM/WAVE – Maintain Waves.

SAP Extended Warehouse Management (SAP EWM)

510

772

SAP Online Help

20.07.2007

Automatic Wave Assignment Purpose You can automate the assignment of warehouse request items [Seite 109] to waves [Seite 769]. Extended Warehouse Management (EWM) uses the condition technique [Extern] to determine wave templates. This enables EWM to determine which wave template [Seite 767] corresponds to certain data from the header, item, or split item of a warehouse request. For more information, see Wave [Seite 769].

Prerequisites ●

You have created wave templates. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Wave Management → /SCWM/WAVETMP – Maintain Wave Templates.

●

In Customizing, you have defined the conditions for wave template determination. Here you have defined the following: ○

Key or combination of fields that EWM uses to determine wave templates

○

Access sequence

○

Condition types and their assignment to access sequences

○

Determination procedures

○

Assignment of determination procedures to document types

○

Condition maintenance groups

For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Wave Management → Wave Template Determination. ●

You have created condition records that connect the conditions and wave templates. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Wave Management → /SCWM/WDGCM – Maintain Conditions for Determining Wave Templates.

●

You have set the Automatic Wave Creation indicator for the warehouse process type in which the warehouse request item is found. For more information, see the IMG for EWM under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type.

Process EWM performs automatic wave assignment as follows: ...

EWM has multiple warehouse request items. 1. EWM uses the condition technique to determine valid wave templates for the delivery for each warehouse request item. 2. For each wave template, EWM determines whether the wave to be created lies within the period of time between the actual point in time and the planned completion time for the warehouse request item. The actual point in time is the current system date and system time. Depending on whether a relevant wave exists already, and whether it has already been released, EWM uses this wave or creates a new one.

SAP Extended Warehouse Management (SAP EWM)

510

773

SAP Online Help

20.07.2007

Detailed Process Choose...

1. After you or EWM have created or changed a warehouse request, EWM creates a Post Processing Framework action (PPF action). 2. You start to process the PPF action. On the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Print → SPPFP - Display and Process PPF Actions. 3. Depending on your settings for the condition technique, EWM determines one or more valid wave templates for each item or split item in the warehouse request. 4. EWM reads the attribute data for each wave template. 5. EWM determines the following times: ○

EWM determines the planned completion time of the warehouse request item and the wave completion time for each item or split item in a warehouse request that EWM has not yet assigned to a wave.

EWM liest das...

■

Planned completion time for warehouse request item For stock removal, EWM uses the planned date and the planned time for Departure from Yard. If these dates are not available, EWM uses the dates for the goods issue start for outbound deliveries. In the case of internal stock transfers or posting change deliveries, EWM uses the dates from the date/time category Warehouse Activities End Date/Time.

■

Wave completion time EWM determines the date and time for wave completion for each wave template option. If the planned completion time for the warehouse request item is before the wave completion time specified in the template option, EWM sets the wave completion date to that of the day before the planned completion date for the warehouse request item. If the planned completion time of the warehouse request item is after the wave completion time or is the same as the wave completion time specified in the wave template option, EWM sets the wave completion date to the planned completion date of the warehouse request item. EWM changes only the wave completion date on the basis of the situations described. The following figure shows the complete situation:

SAP Extended Warehouse Management (SAP EWM)

510

774

SAP Online Help

20.07.2007

In the first case, the planned completion time of the warehouse request item is 13:00 on day 2. The planned wave completion time is 15:00 on day 2. As such, the planned completion time of the warehouse request item occurs before the wave completion time that you specified in the wave template option. EWM schedules the wave to be created with the wave completion date of the day before the planned completion date of the warehouse request item, in other words, 15:00 on day 1. In the second case, the planned completion time of the warehouse request item is 15:00 on day 1. The planned wave completion time is 13:00 on day 1. As such, the planned completion time of the warehouse request item occurs after the wave completion time that you specified in the wave template option. EWM schedules the wave to be created with the wave completion date on the same day as the planned completion date of the warehouse request item, in other words, 13:00 on day 1.

EWM calculates the dates for a wave template option in accordance with the calendar that you have specified in the wave template. ○

Lock time EWM calculates the lock date, lock time, release date, and release time using the date and time of the wave completion.

If any of these times are before the actual point in time, the wave template option is invalid. 6. EWM attempts to find a valid wave template. ○

If the dates and times for the lock and the release are after the actual point in time, the wave template option is valid and EWM uses all the dates in the wave template.

SAP Extended Warehouse Management (SAP EWM)

510

775

SAP Online Help

20.07.2007

○

If the dates and times for the lock and the release are before the actual point in time, the wave template option is not valid and EWM does not use the wave template option with this date.

○

If EWM does not find a valid wave template option in the past for an item or split item in a warehouse request, EWM executes the following (“In the past” refers to the planned completion time of the warehouse request item, but the determination of a valid wave template still occurs after the actual point in In terms of time, determination of a valid wave template always occurs after the actual time i.

EWM determines the date and time for the wave completion. If the planned completion time of the warehouse request item is either before the wave completion time or is the same as the wave completion time, EWM sets the wave completion date to the day after the planned completion date. If the planned completion time of the warehouse request item is after the wave completion time, EWM sets the wave completion date to the planned completion date of the warehouse request item.

ii.

EWM then determines the date and time for wave completion for each wave template option (see step 5).

iii.

If EWM does not find a valid wave template, it adds a day to the wave completion date. EWM repeats the calculation for the wave completion time and the lock time.

7. EWM determines the sequence for the best wave template and wave template option. To do this, EWM sorts the wave templates that were determined according to the level number and counter number in the determination procedure of the condition technique and according to the access number of the access sequence. Within the same level number, counter number and access number, EWM sorts the wave templates and wave template options that were determined by the wave completion time that is closest to the planned completion time of the warehouse request item. This means that the wave template option with the wave completion time closest to the planned completion time is first within a block of possible waves for the same level number, counter number and access number. 8. EWM transfers the results, in other words, all valid wave templates and wave template options for each item or split item in a warehouse request to Business Add-In (BAdI) /SCWM/EX_WAVE_PLAN, method CHANGE_WAVES. 9. EWM assigns a wave or wave template to each item or split item in a warehouse request. EWM checks whether a wave already exists for this wave template option. ○

If no corresponding wave exists, EWM creates a new wave with the wave template option that was determined. EWM assigns the item or split item in the warehouse request to this wave. If an exception occurs, the wave template option is invalid. For example, the wave exceeds the wave capacity. EWM then attempts to create a corresponding wave using the next wave template option.

○

If a corresponding wave exists already, EWM assigns the item or split item in the warehouse request to this wave. If an exception occurs, the wave template option is invalid. For example, the wave exceeds the wave capacity. EWM then attempts to create a corresponding wave using the next wave template option.

○

If a corresponding wave exists already and has been released, EWM attempts to create a corresponding wave with the next wave template option. EWM then assigns the item or split item in the warehouse request to this wave.

SAP Extended Warehouse Management (SAP EWM)

510

776

SAP Online Help

20.07.2007

You can permit exceptions by setting the Wave Assignment Also Possible After Wave Release indicator. This enables you to assign another warehouse request item to a wave that has already been released, in other words, the wave template option is valid in this instance.

Example The following figure provides an example of how EWM creates a wave:

In the first case, wave template option C does not lie within the period between the current point in time and the planned completion date of the warehouse request item. It is therefore invalid. Wave template options A and B lie within the period between the actual point in time and the planned completion date of the warehouse request item. Wave template option B is closest to the planned completion date of the warehouse request item, and is therefore the best wave template option. In the second case, all the wave template options lie outside the period between the actual point in time and the planned completion date of the warehouse request item. They are therefore all invalid. EWM first determines the wave template option that is the closest to the planned completion of the warehouse request item, in other words, wave template option B is the best wave template option.

SAP Extended Warehouse Management (SAP EWM)

510

777

SAP Online Help

20.07.2007

Two-Step Picking Purpose In the case of two-step picking, the picking process is split into two separate steps. You optimize the picking process by collectively removing products from your warehouse for multiple outbound deliveries in the first step, and assigning the products that you have withdrawn to the relevant outbound deliveries in the second step. In this way, you pick a large number of outbound deliveries on a collective basis. Another advantage of two-step picking is that you can minimize the total number of picking operations performed during picking, by removing the total required quantity of the products in a cross-requirement way in the first step. Moreover, stock removal and allocation are two separate warehouse processes. You create a separate warehouse task for each of these steps.

Prerequisites ●

You have activated two-step picking in Customizing for Extended Warehouse Management (EWM). If you want to define the two-step process on a product basis, set the 2-Step Matl-Dep. indicator as well. EWM uses this indicator to determine in the product master record on the Warehouse Data tab page whether you want to pick this product directly from the warehouse or whether you intend to use two-step picking for this product. For more information, see the Implementation Guide (IMG) for EWM under Goods Issue Process → Wave Management → General Settings → Set Up Two-Step Picking in the Two-Step Pick field or the 2-St. Matl-Dep. indicator.

●

You have defined a warehouse process type for the first picking step. In the standard system, warehouse process type 2020 is defined for the first picking step. For more information, see the IMG for EWM under Cross-Process Settings → Warehouse Task → Define Warehouse Process Type.

●

You have assigned the warehouse process type for the first picking step to the warehouse number. For more information, see the IMG for EWM under Goods Issue Process → Wave Management → General Settings → Set Up Two-Step Picking in the Process Type field.

●

You have created a storage type and storage bins for the intermediate storage section. In the standard system, storage type 2010 is defined. For more information, see the IMG for EWM under Master Data → Define Storage Type and Master Data → Storage Bins → Define Storage Bin Structure.

●

The stock removal strategy for the second picking step must find the storage type of the intermediate storage section. You control this by setting the 2 indicator for two-step picking in Customizing for the storage type search sequence. For more information, see the IMG for EWM under Goods Issue Process → Strategies → Determine Storage Type Search Sequence for Stock Removal.

●

You have combined the outbound deliveries into a wave. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Wave Management → /SCWM/WAVE – Maintain Waves.

Process The following figure provides an overview of two-step picking:

SAP Extended Warehouse Management (SAP EWM)

510

778

SAP Online Help

20.07.2007

Two-step picking splits the picking process in the warehouse into two separate steps: ...

1. In the first picking step, in other words, withdrawal, the following substeps occur: a. You combine the outbound deliveries into a wave. For more information about creating waves, see Waves [Seite 769]. b. As soon as you form a group of outbound deliveries, EWM determines the relevance of the corresponding products to two-step picking You can change the relevance of the entire wave to two-step picking by changing the value in the Two-Step Pick. field on the user interface for wave maintenance (no entry = not relevant, Two = two-step picking). c. You create the withdrawal warehouse tasks for the wave, in other words, wave release for the withdrawal step. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Work Scheduling → Wave Management → Maintain Waves. Select the wave and then choose the Release Withdrawal pushbutton. As a result, the release of the first step of picking is completed. d. You pick the entire product quantity to fulfill the requirements from multiple deliveries. e. You execute the goods movements for the withdrawal step and transfer the products that you have picked for the group from source storage bins [Extern] to an intermediate storage section. f. You confirm the warehouse tasks for the withdrawal step and, in doing so, you confirm that the necessary products are in the intermediate storage section. You have completed the first step of two-step picking (withdrawal). 2. In the second picking step, in other words, allocation, the following substeps occur: a. You create warehouse tasks for the allocation step, in other words, wave release for the allocation step. In doing so, you distribute the total quantity that has been picked among the individual requirements. b. You transport the products that belong to a wave from the intermediate storage section to the destination storage bins (for example, to a goods issue zone or packing station).

SAP Extended Warehouse Management (SAP EWM)

510

779

SAP Online Help

20.07.2007

c. You confirm the warehouse tasks for the allocation step and, in doing so, you confirm that the necessary products are in the destination storage bins. You have completed the second step of two-step picking (allocation).

Result You have performed two-step picking.

SAP Extended Warehouse Management (SAP EWM)

510

780

SAP Online Help

20.07.2007

Radio Frequency Framework Use Extended Warehouse Management (EWM) includes the implementation of a radio frequency (RF) framework satisfying the following objectives: ●

Decouples business logic from the physical presentation of application data on a selected presentation device [Extern]

●

Supports a large variety of device sizes, device types, and data entry types

●

Provides appropriate forms of data presentation according to application data, device capabilities, and user preferences

●

Calls appropriate services according to resource inputs (such as verification/input data, keystroke, or logon request)

●

Enables personalized menus [Extern] and screens

●

Enables flexible and user-friendly screen and flow logic generation and modification

By providing an RF framework, greater efficiency and fast, error-free data communication can be attained in the warehouse, through the use of mobile RF devices.

Features Support for GUI and Character-Based Devices and Browser-Based Devices The RF framework supports both GUI and character-based devices, as well as browserbased devices. GUI devices are connected to the SAP System just like any other client-dependent PC. The screens can be touch screens, using predefined pushbuttons, or they can be operated using a keyboard. If you are using touch screens, you simply "touch" the appropriate positions on the touch screen instead of clicking with the mouse on a pushbutton. Character-based devices are linked to the system through SAPConsole. SAPConsole operates on a Windows NT/Windows 2000 platform and interacts with the RF terminals connected to it. This concept is currently supported by the leading providers of RF terminals. The system uses the WebSAPConsole for connecting browser-based devices.

Bar Code Support The RF framework supports the use of bar codes for identification and verification purposes. SAP currently supports EAN 128 bar code types, but you can also support other types within the RF framework. Screen Layout Personalization Using the RF screen manager, you can customize the appearance of RF presentation screens, so as to ensure that they are consistent with the attributes of the presentation devices being used. For more information about the RF screen manager, see the Implementation Guide (IMG) for Extended Warehouse Management → Mobile Data Entry → Radio Frequency (RF) Framework → RF Screen Manager.

SAP Extended Warehouse Management (SAP EWM)

510

781

SAP Online Help

20.07.2007

SAP provides screens based on a screen size of 8x20. Menu Personalization Using the RF menu manager, you can define your own menus and menu hierarchy for the RF device transactions. For more information about the RF menu manager, see the IMG for Extended Warehouse Management → Mobile Data Entry → Radio Frequency (RF) Framework → RF Menu Manager

SAP provides a standard menu and menu hierarchy. Standard RF Functionalities The SAP RF framework provides standard RF functionalities, including the following: ●

Logon [Seite 790]

●

Logoff [Seite 793]

●

Recovery [Seite 794]

●

Work execution transactions for the following warehouse processes: ○

Picking [Seite 804]

○

Putaway [Seite 800]

○

Loading [Seite 798]

○

Unloading [Seite 798]

○

Deconsolidation [Seite 799]

○

Packing [Seite 807]

○

Physical Inventory [Seite 808]

○

Replenishment

SAP Extended Warehouse Management (SAP EWM)

510

782

SAP Online Help

20.07.2007

RF Navigation Purpose This section describes the process for navigating from RF menus [Extern] to transactions [Extern], as well as navigation within transactions.

Process Menu Navigation The RF framework supports the following options for menu navigation to RF transactions: 1. Standard Navigation You choose the required menu item. 2. Direct Navigation to Transaction You enter the number of the required menu item displayed, in the Menu field. 3. Virtual Navigation Unlike the first options where navigation is accomplished from the displayed menus, this option enables “virtual” navigation between menus. You enter the numbers of all required menu items, including those not displayed on the current screen, but rather displayed on subsequent screens.

If on the main menu screen, you enter 415 in the Menu field, you navigate to the Pick by HU transaction.

Menu Items

Menu Field

Transaction Navigation When in the screen for a particular logical transaction, you may be required to enter data, validate existing data, or a combination of both.

SAP Extended Warehouse Management (SAP EWM)

510

783

SAP Online Help

20.07.2007

When data entry is required, the input field is open. You enter the data by scanning bar codes. If you enter data manually, you choose Enter after entering the value. Where the content provider fills fields with content, the input fields may either be closed, or hidden (depending on Customizing for Extended Warehouse Management → Mobile Data Entry → Radio Frequency (RF) Framework → Define Logical Transaction Step Profiles → Define Validation Profile). Where the input fields are closed, you verify the values by scanning the bar codes. After all input fields on the screen are filled, one of the following occurs: ●

If the Skip Shortcut indicator is set, the posting (for example, WT confirmation) is automatically triggered.

●

If the Skip Shortcut indicator is not set, you automatically navigate to the Shortcut field.

You can set the Skip Shortcut indicator when maintaining screens via the RF screen manager. For more information, see the Implementation Guide (IMG) for Extended Warehouse Management → Mobile Data Entry → Radio Frequency (RF) Framework → RF Screen Manager. You can invoke functions by choosing the corresponding function key [Seite 786] pushbutton, or entering the function key in the Shortcut field. Where necessary, you enter exception codes in the Shortcut field (for example, for differences).

You define exception codes in Customizing for Extended Warehouse Management → Cross-Process Settings → Exception Handling → Define Exception Codes.

Input Field (Closed)

V

SBin

V

Input Field (Open)

Verification Field (Open)

Navigation Pushbuttons

SrceHU Product

Verification Field (Closed) F1 Prnt

F7 List

F8 Splt

>

Function Keys

SAP Extended Warehouse Management (SAP EWM)

Shortcut Field

510

784

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

785

SAP Online Help

20.07.2007

RF Function Keys Use Function keys are provided with the RF framework.

Features Standard Functions Keys Standard function keys are not displayed in the function key line of an RF screen. Rather, they are accessed directly via the function key or shortcut. Function

Function Key

Shortcut

Description

More

F5

05

Displays the next pushbuttons in the sequence (in case of more than four push pushbuttons for a screen)

Clear

F6

06

Clears a selected input field, or all input fields

Back

F7

07

Returns to previous screen/step

List

F8

08

Displays the list screen (showing the possible input values) for a selected field

Full Message

F9

09

Displays the full message on a separate screen

Transaction-Specific Function Keys Transaction-specific function keys are displayed in the function key line. If more than four function keys/pushbuttons exist for a screen, > is displayed, and you can then choose F5 to display the other pushbuttons.

The following list includes only those function keys that appear as pushbuttons on the user interface. Function

Pushbutton Text

Description

Bin Empty

EmBn

Reports that the storage bin being counted is empty

Close HU

Close

Ends work on a putaway HU

Clear All

ClrAll

Clears the contents of all input fields on the screen

Clear Sum

ClSum

Resets the quantity to zero during counting, or resets the zero stock indicator

Condense HU

Cond

Condenses a nested deconsolidation HU into a single-level HU

Convert HU

Conv

Converts a deconsolidation HU to a putaway HU

Delete HU

Delete

Deletes an HU

Delete HU

DelHU

Deletes a selected HU from the list

Details

Detail

Displays the WO details

Empty Bin

EmBn

Reports that the bin is empty

SAP Extended Warehouse Management (SAP EWM)

510

786

SAP Online Help

20.07.2007

HU Completed

HUCmp

Reports that the HU content count is complete (HU content is not counted, but rather taken as the system quantity)

Create HU

HUCr

Enables you to create a pick HU. If a pick HU is already assigned to the WO, the system displays the number of the existing HU

HU Details

HUDet

Displays details of a selected HU

HU Empty

HUEmp

Reports that the HU is empty

HU Overview

HUOv

Displays the HU overview

HU Screen

HUScr

Navigates you to the HU screen

HU Withdrawal

HUWd

Reports that you have picked the whole pallet

HU Items List

ItList

Displays the items (product and lower-level HUs) of an HU

HU List

List

Lists all the HUs

Nested HUs

N.HUs

Enables you to pick from the lower-level HUs of a nested HU

New Item

NewItm

Enables you to create a new product

Not Existing

NotEx

Reports that the HU does not exist at this location

Pick HU Introduction

PHUIn

Takes you to the pick HU introduction screen (screen 0200)

Product Details

PrdDet

Displays details of a selected product

Print

Prnt

Prints information based on BAdI /SCWM/PRINT_RF, method PRINT_WO_HU

Product

Prod

Navigates you to a screen where you can scan a product number, and the relevant WTs are displayed

Product Details

ProDe

Shows detailed product data

Propose Bin

Prop

Proposes a new bin for the product or HU WT

Recover Resource

RcvRe

Enables you to select a resource with which to continue working (in the case of work interruption when you were logged on to more than one resource)

Reverse

Revers

Reverses the order of entries in the list

Remaining Quantity

RQty

Enables you to report the remaining quantity, during a zero stock check

Reverse Sequence

RvSeq

Reverses the sequence of WTs in a WO

Skip

Skip

Skips the entry and starts at the next one in the list

Skip to End

SkiptE

Places the current entry to the end of the list

Stock Overview

StOv

Displays available stock of a selected product

Select WT

WT

Navigates you to a screen where you can scan a WT number, and then display the WT

WT List

WTLst

Displays the list of WTs in the WO

Unassign

Unasn

Enables you to unassign a WO from your resource

Yes or No

Yes/No

Answers a query message

Zero stock

ZeroSt

Reports that the product count for the storage bin is zero, thus setting the zero stock indicator

SAP Extended Warehouse Management (SAP EWM)

510

787

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

788

SAP Online Help

20.07.2007

Standard RF Functionalities Use The RF framework supports standard RF functionalities, including the following: ●

Logon [Seite 790] and logoff [Seite 793] – implemented as steps [Extern] within a master transaction [Extern]

●

Recovery [Seite 794] – implemented as a state of the logon step

●

Request work/inquiry – implemented as a step of the master transaction, which initiates another transaction

SAP Extended Warehouse Management (SAP EWM)

510

789

SAP Online Help

20.07.2007

Logon Use Logon to the RF environment enables the tracking of resources [Seite 752], stock on resources, and warehouse order (WO) selection [Seite 757]. After logging on to the system, a resource can operate as an active resource, which can request and execute work in the warehouse.

Prerequisites You have logged on to the system.

Features Automatic and Manual Logon The RF framework supports automatic logon triggered by a presentation device [Extern], or triggered by a user. ●

Triggered by Presentation Device (Background Processing) If a presentation device can identify itself (for example, by IP address), the application uses this identification to determine the default resource. User-related parameters are based on the predefined user’s default data.

●

Triggered by User If a default resource and warehouse are defined for a user, and a default presentation device is defined for the default resource, then automatic logon occurs when the user chooses to logon to the RF environment. Depending on Customizing, the user may either be logged on automatically, or presented with the Logon screen, with all default parameters displayed.

For manual logon, a user must identify the resource to which he or she logs on, as well as the warehouse and presentation device. Multiple Logons The RF framework supports the logging on of a user to multiple resources.

Activities Logon Automatic Logon Triggered by Device 1.

Manual Logon

Triggered by User

You define a user, using the user maintenance transaction (Extended Warehouse Management → Master Data → Resource Management → /SCWM/USER - Maintain User on the SAP Easy Access screen).

SAP Extended Warehouse Management (SAP EWM)

510

790

SAP Online Help

2.

3.

When defining the user, you must assign a default resource and default warehouse.

You define a presentation device, using the presentation device maintenance transaction (Extended Warehouse Management → Master Data → /SCWM/PRDVC Maintain Presentation Devices on the SAP Easy Access screen).

20.07.2007

When defining the user, you must define a default resource and default warehouse. The default resource must have assigned to it a default presentation device. ●

The device is defined in Extended Warehouse Management → Master Data → /SCWM/PRDVC Maintain Presentation Devices on the SAP Easy Access screen.

●

The device is assigned using the resource maintenance transaction (Extended Warehouse Management → Master Data → Resource Management → /SCWM/RSRC – Maintain Resource on the SAP Easy Access screen).

When defining the presentation device, you must have assigned to it the default resource. The presentation device is one that is able to identify itself.

4.

When you turn on the presentation device, it calls SAPConsole, which initiates the RF presentation transaction, and logs on automatically.

On the SAP Easy Access screen, you choose Extended Warehouse Management → Execution → /SCWM/RFUI - Log On to RF Environment. ●

If you set the Auto Logon indicator when defining the user, you are logged on automatically.

●

If you did not set the Auto Logon indicator, the Logon screen appears, with the fields being filled with the default parameters. You may either keep the default, or change any of them. You then choose Enter to log on.

On the SAP Easy Access screen, you choose Extended Warehouse Management → Execution → /SCWM/RFUI Log On to RF Environment. The Logon screen appears. You enter the warehouse number, resource and presentation device with which to log on. One or more of these fields may be filled with default parameters, depending on your user and resource definitions.

If you do not fill the DefPresDvc field on the Logon screen, it is filled with one of the following: ●

The default presentation device defined for the resource in the resource maintenance transaction

●

The presentation device set as the default in the presentation device maintenance transaction, if no default presentation device is defined for the resource

You choose Enter to log on.

If you set the Auto Logon indicator, multiple logons are not possible.

SAP Extended Warehouse Management (SAP EWM)

510

791

SAP Online Help

5.

20.07.2007

During logon, the Dynpro layer identifies the display profile [Extern] assigned to the specific presentation device. The business logical layer does the following: Addresses the logon to resource management [Seite 750], to perform the logon process Fetches the resource’s personalization profile [Extern] and authorization information. Determines the logical transaction [Extern] associated with the physical transaction ●

Sets the initial step and function code [Extern]

The logon transaction ends only when you log off [Seite 793].

SAP Extended Warehouse Management (SAP EWM)

510

792

SAP Online Help

20.07.2007

Logoff Use This function enables a resource [Seite 752] to log off from the RF environment.

Integration Logoff is a step of the logon [Seite 790] logical transaction [Extern].

Activities ...

1. You choose F1 Logoff. 2. You enter a reason code for logging off and choose F1 Save. The resource’s logoff request is sent to resource management [Seite 750], via the business logic layer package. The resource is logged off from the RF environment. Depending on the reason code, the WOs assigned to the resource either remain assigned to it, or are unassigned.

SAP Extended Warehouse Management (SAP EWM)

510

793

SAP Online Help

20.07.2007

Recovery Use During logon [Seite 790], the system checks with the content provider whether the user is logged on as a resource [Seite 752], and if so, whether he or she was interrupted during WO execution.

Integration The recovery functionality is part of the logon transaction [Extern].

Activities ...

1. A user attempts to log on to the system. 2. The system checks with the content provider whether the user was previously logged on to the RF environment. a. If the user was logged on to a resource, see step 3. b. If the user was logged on to more than one resource, the logon screen is displayed with the RcvRe pushbutton, enabling the user to select the resource with which to continue. 3. The system checks whether a specific WO that was assigned to the resource was stopped before completion. It does so by checking for WOs that fulfill all of the following conditions: a. The WOs are assigned to the resource b. The WOs have already been started c. The WOs can be locked 4. If the system finds any WOs that fulfill these conditions, it does the following: a. Finds the relevant logical transaction b. Finds the WO’s data c. Displays the screen of the relevant step [Extern] 5. If the system does not find any WOs that fulfill these conditions, the system displays the Menu screen.

SAP Extended Warehouse Management (SAP EWM)

510

794

SAP Online Help

20.07.2007

Position Management Use Position management enables an RF device user to validate handling units (HUs) by their position number, rather than by their HU number. This is particularly useful when the HU number tags are not readily accessible, such as when the HUs are stacked on top of each other.

Prerequisites In Customizing for Extended Warehouse Management → Cross-Process Settings → Resource Management → Define Resource Types, you have selected one of the following options for the Pos.Mgmt field: ●

Manual

●

Automatic

Activities ...

1. An RF user logged on as a resource [Seite 752] navigates to the pick HU introduction screen (0200) and scans a pick HU. 2. If the resource’s resource type [Seite 753] has automatic position management, the following occurs: a. The scanned HU is assigned to the next available position. b. The cursor moves to the next HU input field. 3. If the resource’s resource type has manual position management, the following occurs: a. The cursor moves to the position field. b. The resource manually enters the position number. c. The HU is assigned to the position. d. The cursor moves to the next HU input field. 4. In the background, an internal warehouse task (WT) is created to update the HU location and logical position.

SAP Extended Warehouse Management (SAP EWM)

510

795

SAP Online Help

20.07.2007

Position: 4 Position: 3

Position: 1

Position: 2

SAP Extended Warehouse Management (SAP EWM)

510

796

SAP Online Help

20.07.2007

Work Processing Using Radio Frequency Use Work processing provides you with all the functions required to carry out your putaway and stock removal activities. ●

●

●

For the goods receipt process: ○

Unloading Using Radio Frequency [Seite 798]

○

Deconsolidation Using Radio Frequency [Seite 799]

○

Putaway Using Radio Frequency [Seite 800]

○

Confirmation Correction Using Radio Frequency [Seite 803]

For goods issue: ○

Picking Using Radio Frequency [Seite 804]

○

Packing Using Radio Frequency [Seite 807]

○

Loading Using Radio Frequency [Seite 798]

For internal warehouse processes: ○

Physical Inventory Using Radio Frequency [Seite 808]

○

Ad Hoc Movement Using Radio Frequency [Seite 809]

○

Yard Movement Using Radio Frequency [Seite 811]

○

Queries Using Radio Frequency [Seite 812]

○

Resource Management Using Radio Frequency [Seite 814]

○

Handling-Unit-Differenzen mit Radio-Frequency [Seite 815]Handling Unit Differences Using Radio Frequency [Seite 815]

If you are working with products that are hazardous-substance-relevant in warehouse activities, the system shows this with the HazS (hazardous substance) indicator on the respective RF display. If hazardous-substance-relevant texts exist, you can display them using the F9 function key.

SAP Extended Warehouse Management (SAP EWM)

510

797

SAP Online Help

20.07.2007

Loading and Unloading Using Radio Frequency Use You can also execute loading and unloading using a radio frequency presentation device (RF presentation device).

Prerequisites ●

You have logged on [Seite 790] in the RF environment.

●

You have defined a warehouse order creation rule of the type Load/Unload and have specified the number of loading employees who are to execute the higher-level warehouse order in Customizing for Extended Warehouse Management (EWM) under Cross-Process Settings → Warehouse Order → Define Creation Rule for Warehouse Orders.

Features You can use this function to have multiple loading employees load or unload a transportation unit [Seite 613], even if the entire transportation unit corresponds to only one warehouse order. In this case, the system creates a higher-level warehouse order that contains all WTs for the HUs of the transportation unit.

Activities The following describes an example of unloading a truck with four HUs and two loading employees. Loading works in the same way. 1. When the system finds a warehouse order creation rule of the type Load/Unload, it creates a higher-level warehouse order with four WTs. 2. In accordance with the warehouse order creation rule, the system creates two warehouse orders for the two loading employees who are to unload the HUs. These two warehouse orders are linked to the higher-level warehouse order, but do not have any WTs. 3. The system transfers the two warehouse orders as executable to resource management. They are now ready to be processed in the RF environment. 4. The system transfers the two warehouse orders to the two loading employees. They go to the relevant trucks (in accordance with the warehouse order). 5. As soon as the two loading employees scan the first HU, the system automatically moves the relevant WT from the higher-level warehouse order to the warehouse order belonging to the relevant loading employee. 6. Both loading employees unload all the HUs and confirm the corresponding WTs. The higher-level warehouse order no longer contains any WTs, since the system has distributed them to the lower-level warehouse orders. After the loading employees have confirmed the last WT, all warehouse orders involved are completed (in other words, confirmed or canceled). This would also be the case, even if only one loading employee had unloaded the truck.

SAP Extended Warehouse Management (SAP EWM)

510

798

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

799

SAP Online Help

20.07.2007

Putaway Using Radio Frequency Use You can execute putaways using a radio frequency presentation device (RF presentation device).

Prerequisites You have logged on [Seite 790] in the RF environment. The destination storage bins of the warehouse orders [Seite 419] to be processed are always in the same activity area.

Features Putaway According to Handling Unit (HU) You enter a handling unit number (HU number) and the system searches for the corresponding warehouse order or warehouse orders. Putaway According to HU (Collective) You enter more than one HU number and the system searches for the corresponding warehouse orders. Putaway According to Warehouse Order You enter a warehouse order number and the system displays the warehouse tasks assigned to the warehouse order that are to be executed.

Activities Putaway According to Handling Unit (HU) 1. You enter a HU number. EWM thus includes the HU in the resource. 2. The system searches for the corresponding warehouse orders. 3. The system displays the following: ○

If the system finds a WT for the entire HU, the system displays the source data (HU number, destination storage bin).

○

If the system finds WTs for the products in the HU, then you are dealing with a distributive putaway [Extern]. The system displays the first WT it has found according to the sort sequence of the destination storage bins. The system displays the following data: ■

Source HU

■

Product

■

Quantity

■

Batch

■

Destination HU

SAP Extended Warehouse Management (SAP EWM)

510

800

SAP Online Help ■

20.07.2007

Destination storage bin

If a warehouse order has more than one WT, you can do the following: ○

You can skip a WT.

○

You can reverse the sequence in which the system displays the WTs.

○

You can place the displayed WT at the end of the execution.

4. You confirm the data of the HU WT or of the first product WT. 5. If a warehouse order has more than one product WT, the system displays the data of the next product WT and the action repeats itself. Putaway According to Handling Unit (Collective) ...

1. You enter all desired HU numbers. 2. You decide whether you want to putaway further in a guided manner or according to product number or warehouse task. 3. The system searches for the corresponding warehouse task. 4. The further steps correspond to steps three to five for putaway according to handling unit. Putaway According to Warehouse Order ...

1. You enter a warehouse order number. 2. The system searches for the corresponding warehouse tasks. 3. The system displays the source data (product, quantity, batch, and source storage bin) of the first product WT that belongs to the warehouse order, or the source data (HU and source storage bin) of the first HU WT that belongs to the warehouse order. If a warehouse order has more than one WT, you can do the following: ○

You can skip a WT.

○

You can reverse the sequence in which the system displays the WTs.

○

You can place the displayed WT at the end of the execution.

4. You confirm the source data of the first product WT or the source data of the first HU WT. 5. The system displays the destination data of the product WT (product, quantity, batch, and destination storage bin), or the destination data of the HU WT (HU and destination storage bin). 6. You confirm the destination data of the first WT. 7. If a warehouse order has more than one WT, the system displays the source data of the next WT (product WT or HU WT), and the action repeats itself.

Exceptions to Putaway Using RF HU WT Confirmation You can specify an exception for this process and then: ●

Change the destination storage bin

●

In general, skip the HU WT that is currently to be processed For example, if the aisle is blocked, you cannot get to the source storage bin or destination storage bin. During the putaway process, then, the system no longer shows you this HU WT and you do not need to confirm the source data and destination data.

SAP Extended Warehouse Management (SAP EWM)

510

801

SAP Online Help

20.07.2007

Product WT Confirmation You can specify an exception for this process and then: ●

Change the destination storage bin

●

Record differences For example, if a piece of the product quantity is damaged, you can enter a smaller product quantity rather than confirm the quantity.

●

Change the batch

●

In general, skip the product WT that is currently to be processed For example, if the aisle is blocked, you cannot get to the source storage bin or destination storage bin. During the putaway process, then, the system no longer shows you this HU WT and you do not need to confirm the source data and destination data.

SAP Extended Warehouse Management (SAP EWM)

510

802

SAP Online Help

20.07.2007

Confirmation Correction Using Radio Frequency Use You can also use a radio frequency device (RF device) to correct warehouse tasks in the goods receipt process that have already been confirmed.

Prerequisites ●

You have logged on [Seite 790] in the RF environment.

●

You have defined a completion delay for inbound deliveries (see Confirmation Correction [Seite 311], under “Prerequisites”).

●

You are using a document type and item type with a status profile for which you have activated the status DWM (see Confirmation Correction [Seite 311], under Prerequisites).

Features You can specify the following selection criteria for putaway warehouse tasks (putaway WTs): ●

Warehouse order (WO)

●

Putaway WT or a stock identification

●

Storage bin

In each case, the system shows you the assigned putaway WTs for the correction. You can correct the batch and the quantity. The system then adjusts the posted stock correspondingly.

Activities ...

1. You specify the selection criterion, such as confirmation correction by WO, and the warehouse order number. 2. The system displays the relevant putaway WTs. 3. You choose ^ (Page up) or v (Page down) to navigate to the putaway WT you want to correct. 4. You specify an exception code. This renders the fields Btch (batch) and AQty (quantity) ready for input. 5. You enter the changes and save them by choosing ENTER.

SAP Extended Warehouse Management (SAP EWM)

510

803

SAP Online Help

20.07.2007

Picking Use You are able to execute picking using an RF presentation device.

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

Features ...

System-Guide Picking The system presents the optimal WO for execution, pursuant to the WO selection [Seite 757] mechanism. System-Guided Picking by Queue You enter a queue [Seite 764] (from one of your allowed queues), and the system presents for execution the optimal WO from the queue, pursuant to the WO selection mechanism. Picking by WR You enter a WR number, and the system finds the corresponding WO. Picking by WO You enter a WO number, and the system presents the WO for execution. Picking by HU You enter an HU number, and the system finds the corresponding WO.

SAP Extended Warehouse Management (SAP EWM)

510

804

SAP Online Help

20.07.2007

RF Picking Flow Purpose This section shows the flow of the standard screens, in the context of the logical transactions [Extern] and steps [Extern], when a user performs RF picking.

Process Flow Logical transaction

Selection Step

Pick HU Introduction Step

Source Pick/Removal Step

Destination Placement Step

Screen 0550 Nested HUs System-Guided Picking Screen 0450 Batch Change

Product TO

Screen 0501 Pick Product Step Pick by Queue

Selection Screen 0104

Screen 0503 Pick Bulk For Product TO Step

Screen 0302 Place Product Step

Screen 0420 Stock Check Pick by WR

Selection Screen 0102 Screen 0200 Introduce Pick HU Step

Pick by WO

Selection Screen 0103

Screen 0410 Differences

Screen 0410 Differences

Screen 0800 RF TO List

Screen 0800 RF TO List

Screen 0600 WO Details

Screen 0600 WO Details

HU TO

Screen 0502 Pick HU Step

Screen 0301 Place HU Step Pick by HU

Selection Screen 0101

Screen 0003 List

...

1.

SAP Extended Warehouse Management (SAP EWM)

510

805

SAP Online Help

20.07.2007

RF Picking - Process Flow System-Guided Picking

System-Guided Picking by Queue

Picking By WR

Picking By WO

Picking By HU

1.

After logging on to an RF presentation device [Extern], you choose 04 Goods Issue → 01 RF Picking Main Menu.

2.

You choose 01 System-Guided Picking.

3.

4.

You choose 02 System-Guided by Queue.

You choose 03 Pick by WR.

You choose 04 Pick by WO.

You choose 05 Pick by HU.

You select a queue [Seite 764].

You select a WR [Extern].

You select a WO.

You select an HU.

The system selects and locks a WO for selection, pursuant to the WO selection [Seite 757] mechanism. The pick HU introduction screen appears.

5.

If HUs or packaging products are assigned to the WO, you can use the existing HUs. Otherwise, you can create your own by selecting packaging product, printing labels and scanning the HU numbers.

6.

After introducing one or more pick HUs, you navigate to the source screen of the first TO of the WO. Depending on the TO, one of the following screens is displayed:

7.

●

Pick product screen – if the TO is for picking a quantity of product from a nonbulk storage type

●

Pick bulk product screen – if the TO is for picking a quantity of product from a bulk-storage type

●

Pick HU screen – if the TO is for picking HUs which are not known in the TO

In the case of the pick product screen, you validate the source bin, source HU, product, quantity and destination HU (or position [Seite 795]). In the case of the pick HU screen, you validate the source bin, source HU and destination HU. The pick bulk product screen is the same, except you must scan a source HU number.

8.

After all products are picked, and have been put into the resource’s [Seite 752] pick HUs, the place HU screen appears. In case of no pick HU, the place product screen appears.

9.

In the case of the place product screen, you validate the destination bin, position, product and quantity. In the case of the place HU screen, you validate the destination bin and destination HU.

2.

SAP Extended Warehouse Management (SAP EWM)

510

806

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

807

SAP Online Help

20.07.2007

Physical Inventory Using Radio Frequency Use You can also enter the count results using a radio frequency (RF) device. In this case, you must not print a physical inventory count document [Extern] or transfer the count results from the physical inventory count document to the system. Moreover, the data is transferred to the system in a timely way.

Prerequisites You have logged on [Seite 790] in the RF environment.

Activities You carry out a physical inventory count and enter the count results in the RF device. The device automatically records the count time and the counter. The remaining steps are the same as for physical inventory without radio frequency. For more information, see Physical Inventory [Seite 667].

SAP Extended Warehouse Management (SAP EWM)

510

808

SAP Online Help

20.07.2007

Ad Hoc Movements Using Radio Frequency Use You can carry out ad hoc movements for products and handling units (HUs) using a radio frequency presentation device (RF presentation device).

Prerequisites You have logged on in the RF environment.

Features ●

Log on at a work center. For most transactions within the main menu for the ad hoc movement, you have to log on at a specific work center to receive proposals for different entry fields.

●

You do not select the required data from the stock overview. Instead, you either scan it in or enter it directly: ○

Scan in storage bin

○

Scan in product

○

Manually enter the quantity

○

Manually enter the warehouse process type

○

Manually enter the reason (optional)

●

If a product with different stock characteristics (batches) is contained in the storage bin, you can use a list to select the desired product.

●

For handling units, you cannot unpack or repack the products by creating a product warehouse task in the HU warehouse task.

For more information about ad hoc movements, see Ad Hoc Movements [Seite 415] or Executing an Ad Hoc Movement [Seite 125].

Activities ...

Executing Ad Hoc Movements Using Product WT 1. You manually create a product WT. a. You have to specify the source storage bin and the product. The system displays a further screen if the source storage bin and product specified by you do not lead to a unique stock determination. You select the corresponding stock, for example, product A from the free stock B. You can specify a reason for the ad hoc movement. You can call up the product details. The system displays the following: ■

The product short text

■

If applicable, whether the product contains a hazardous substance If the product contains a hazardous substance, you can view this information by choosing Display Hazardous Substance Detail Information.

SAP Extended Warehouse Management (SAP EWM)

510

809

SAP Online Help

20.07.2007

■

If applicable, the product batch

■

The available quantity in operative unit of measure

If there are more than one stock for the product, you can also display the stock overview for that product. b. You specify the process type so that the system can create the product WT. c. You specify the source quantity in operative or base unit of measure. You can also manually specify the destination storage bin. If you do not enter a destination storage bin, the system determines it according to the storage type putaway strategies. 2. The system creates the product WT. 3. You transfer the products to the destination storage bin and confirm the product WT by scanning at the destination storage bin. If you can only enter an insufficient quantity at the destination storage bin, for example because you have damaged a product during the transfer, you can enter this insufficient quantity and include an exception code. You can use this exception code to trigger follow-up actions that you have defined in Customizing.

Executing Ad Hoc Movements Using HU WT ...

1. You manually create a HU WT. a. You scan the HU. The system displays the following: ■

The source storage bin

■

The HU type

■

If applicable, whether the HU contains a hazardous substance If the HU contains a hazardous substance, you can view this information by choosing Display Hazardous Substance Detail Information.

You can display the contents of the HU for information purposes. b. You specify the process type and a reason (optional) so that the system can create the HU WT. c. You manually enter either the destination storage bin or the destination HU. If you do not enter anything, the system determines the destination storage bin or destination HU according to the storage type putaway strategies. 2. The system creates the HU WT. 3. You transfer the HUs to the destination storage bin or destination HU and confirm the HU WT by scanning the destination storage bin or destination HU.

SAP Extended Warehouse Management (SAP EWM)

510

810

SAP Online Help

20.07.2007

Yard Movement Using Radio Frequency Use You can also execute yard movements in a radio frequency (RF) environment.

Prerequisites You have logged on [Seite 790] in the RF environment.

Activities Create Warehouse Task ...

1. Scan the transportation unit (TU) and specify the standard carrier alpha code (SCAC) or carrier. The system creates a warehouse task (WT) for the handling unit that is assigned to the TU. 2. Confirm the WT on the desktop.

Create and Confirm Warehouse Task ... ...

1. Scan the transportation unit (TU). The system creates a warehouse task (WT) for the handling unit that is assigned to the TU. 2. Confirm the WT by scanning the destination storage bin.

SAP Extended Warehouse Management (SAP EWM)

510

811

SAP Online Help

20.07.2007

Querying Using Radio Frequency Use You can also query the following in a radio frequency (RF) environment: ●

A handling unit (HU)

●

A stock

●

A warehouse order (WO)

Prerequisites You have logged on in the RF environment. On the SAP Easy Access screen, you choose Extended Warehouse Management → Execution → /SCWM/RFUI - Log On to RF Environment. Specify a warehouse number, a resource, and a presentation device. The system displays an overview with menu options. Choose 05 Internal Processes. The system displays the next menu options. Choose 03 Query.

Features You can start queries using both the SAP Easy Access screen and the respective function keys in the RF transactions, such as for picking or putaway. You have the following options when querying using RF: ●

HU query (01 HU Query)

●

Stock query (02 Stock Query)

●

○

By storage bin (01 Stock Query by Storage Bin)

○

By product (02 Stock Query by Product)

WO query (03 WO Query) ○

By WO (01 WO Query by WO)

○

By warehouse task (02 WO Query by WT)

○

By queue (03 WO Query by Queue)

○

By HU (04 WO Query by HU)

Activities HU query ...

1. Scan the HU number. 2. The system displays the corresponding products and, in the case of nested HUs, it also displays lower-level HUs. This means that you can navigate through the whole HU hierarchy up to product detail level. 3. If necessary, display the detailed HU data. If you are working with nested HUs, you can also display the products of all HUs within the HU hierarchy. Additionally, you can navigate back to the highest-level HU. 4. Specify a line number for an HU or a product. The system displays either the corresponding HU level with its products and the lower-level HUs, or the detailed product data.

SAP Extended Warehouse Management (SAP EWM)

510

812

SAP Online Help

20.07.2007

Stock query by storage bin ...

1. Scan the storage bin. 2. The system displays the corresponding products and their quantities. 3. If necessary, display the detailed storage bin data. 4. Enter a line number. The system displays the stock details. Stock query by product ...

1. Scan the product. 2. The system displays the corresponding storage bins and their quantities. 3. If necessary, display the detailed product data or sort the storage bins by stocks in descending order. 4. Enter a line number. The system displays the storage bin details. WO query by WO, WT, or queue ...

1. Depending on the menu option that was selected first, you scan the WO, the WT, or the queue. 2. The system displays the relevant WTs. 3. If necessary, display the detailed WT data. Additionally, you can restrict the WT display to open WTs or confirmed WTs, or you can display all WTs. WO query by HU ...

1. Scan the HU. 2. Choose whether the system searches for WTs that have the scanned HU as the source HU, the destination HU, or both. 3. The system displays the relevant WTs. 4. If necessary, display the detailed WT data. Additionally, you can restrict the WT display to open WTs or confirmed WTs, or you can display all WTs.

SAP Extended Warehouse Management (SAP EWM)

510

813

SAP Online Help

20.07.2007

Resource Management Using Radio Frequency Use You can change the assignment of the default queue, that is, the assignment of the queue that the system checks first to see if any work exists for a resource. Additionally, you can change the assignment of resources to groups [Extern].

Prerequisites ●

You have logged on in the RF environment. On the SAP Easy Access screen, you choose Extended Warehouse Management → Execution → /SCWM/RFUI - Log On to RF Environment. Specify a warehouse number, a resource, and a presentation device. The system displays an overview with menu options. Choose 05 Internal Processes. The system displays the next menu options. Choose 05 Resource Management.

●

When you specify a new queue, you must have defined it within the resource group. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Resource Management → Maintain Queue Sequence for Resource Group.

Features You have the following options for resource management using RF: ●

Changing the queue (01 Change Queue) You can specify a new queue directly or select a new queue via the input help.

●

Changing the resource group (02 Change Resource Group) You can specify a new resource group and a new queue.

SAP Extended Warehouse Management (SAP EWM)

510

814

SAP Online Help

20.07.2007

Handling Unit Differences Using Radio Frequency Use You can enter differences for handling units (HUs) in the radio frequency environment (RF environment).

Prerequisites You have logged on in the RF environment. On the SAP Easy Access screen, you choose Extended Warehouse Management → Execution → /SCWM/RFUI - Log On to RF Environment. Specify a warehouse number, a resource, and a presentation device. The system displays an overview with menu options. Choose 05 Internal Processes. The system displays the next menu options. Choose 07 Enter HU Difference (if necessary, use v to scroll down).

Features You can enter a difference quantity for an HU at product detail level. The system posts the difference quantity according to this exception code, for example, in the goods receipt process at the expense of the supplier.

Activities ...

1. Specify the HU, the warehouse task relevant to this HU that was confirmed last, and an exception code. 2. The system displays the corresponding products and, in the case of nested HUs, it also displays lower-level HUs. This means that you can navigate through the whole HU hierarchy up to product detail level. 3. If necessary, display the detailed HU data. If you are working with nested HUs, you can also display the products of all HUs within the HU hierarchy. Additionally, you can navigate back to the highest-level HU. 4. Specify a line number for an HU or a product. The system displays either the corresponding HU level with its products and the lower-level HUs, or the detailed product data. 5. Specify the quantity difference for an HU at product detail level and book it out.

SAP Extended Warehouse Management (SAP EWM)

510

815

SAP Online Help

20.07.2007

Enhancement Screen Wizard Use In the Enhancement Trigger dialog box, you can choose this option to add or remove fields from a radio frequency (RF) screen.

Features As you go through the process of modifying the RF transition screen, the following features are available: ●

Each time you add or remove fields from the screen, the wizard generates an updated screen. The wizard displays a field catalogue from which you can choose the required fields that you want to display on the screen. The field catalogue displays fields from the corresponding screen structure.

●

You can also choose a field from another screen structure.

When the process is complete, the wizard creates a new screen and adjusts the Customizing to display the enhanced screen only to a specific group of users. If you want to see the new screen, enter the personalization profile. The new screen is displayed in Screen Painter, where you can adjust aspects of the screen layout, such as position and field size.

Run this wizard only if you know the layout of the target screen to be created. The wizard does not check or control the number of fields that can be added to an RF screen. We recommend that you first consider how many fields are required and whether they fit into the target screen.

Example The figure below explains how to run the Enhancement Screen Wizard:

SAP Extended Warehouse Management (SAP EWM)

510

816

SAP Online Help

Start

20.07.2007

Start RFUI Transaction

Simulate a Warehouse Process

Traverse to the screen to be modified

Trigger Enhancement Dialog

Choose Add/Modify fields as enhancement type

In the wizard, choose the required fields on the target screen

End

No Input target screen number

Input Presentation/ Personalization profile

Wizard input complete?

Yes

Finish wizard processing to generate the target screen

SAP Extended Warehouse Management (SAP EWM)

Make further adjustments in the screen painter if required

510

817

SAP Online Help

20.07.2007

Split Screen Wizard Use In the Enhancement Trigger dialog box, you can choose the Split Screen option to split a screen and distribute the existing screen fields across several new screens.

Features As you go through the process of splitting the radio frequency (RF) screen, into multiple screens, the wizard does the following: ●

Displays a field catalogue comprising existing fields from the current screen. You can assign a new screen to each of the fields. You should also specify the screen programs and numbers for each new screen.

●

Displays the screens based on your preferred sequence.

●

Enables you to configure the function codes that are displayed in each resulting screen. When the process is complete, the wizard creates a new set of screens and adjusts the Customizing to display the enhanced screens only to the specified group of users. If you want to see the new screen, enter the personalization profile. Run this wizard only if you know the layout of the target screen to be created. The wizard does not check or control the number of fields that can be added to an RF screen. We recommend that you first think about how many fields are required and whether they fit into the target screen.

Example The figure below explains the steps to run the Split Screen Wizard:

SAP Extended Warehouse Management (SAP EWM)

510

818

SAP Online Help

Start

20.07.2007

Start RFUI Transaction

Simulate a Warehouse Process

Traverse to the screen to be modified

Trigger Enhancement Dialog

Choose Split Screen as enhancement type

In the wizard, assign fields of current screen to new screens

No

Input Presentation/ Personalization profile

Wizard input complete?

Yes

Finish wizard processing to generate the target screens

SAP Extended Warehouse Management (SAP EWM)

End

510

819

SAP Online Help

20.07.2007

Material Flow System (MFS) Purpose The Material Flow System (MFS) enables you to connect up an automatic warehouse to Extended Warehouse Management (EWM) without the need for an additional warehouse control unit. You can set up the MFS in such a way that warehouse tasks (from an identification point to a storage bin in an automatic high-rack storage area, for instance) are subdivided into smaller tasks and these are passed on step by step to the programmable logic controller (PLC) [Extern] responsible in each case via telegram communication. The putaway and removal from storage of handling units (HUs) can thus take place without the use of another software system. You can define capacity limits for communication points [Seite 827], conveyor segments [Seite 828], or resources [Seite 829]. The EWM system then holds back tasks for the PLC as soon as these limits are exceeded. The same applies if the PLC reports that one of the individual elements of conveyance (vehicles, legs, communication points) are subject to malfunction. A warehouse management monitor that is supplied as part of this package enables you to track, evaluate, and influence the process.

Introductory Notes Make the Customizing settings described under Setting Up the Material Flow System [Seite 830].

Integration The MFS is integrated within EWM. It is connected to one or more PLCs.

Features If you use EWM to manage an automatic warehouse, you can use the following functions: ●

Automatic identification of HUs using scanners on the automatic storage retrieval facility.

●

Automatic diversion of non-storable HUs (incorrect contours, excessive weight, unidentified)

●

Fully automatic putaway of HUs in the storage bin via any number of interim steps. These interim steps are represented by communication points [Seite 827].

●

Malfunctions reported by the controls taken into account

●

Capacity limits for communication points, conveyor segments, and vehicles taken into account

●

Reduction in empty traveling paths for stacker cranes through interleaving [Extern]

●

Goods-to-man [Extern] picking principle

●

The stocks are also available for deliveries during transportation within the system.

●

Stable telegram communication between EWM and PLC via parallel, bidirectional communication channels

The warehouse management monitor provides you with the following options:

SAP Extended Warehouse Management (SAP EWM)

510

820

SAP Online Help

20.07.2007

●

Tracking of current state of system

●

Evaluation of telegrams and response times

●

Determination of current location of HUs and identification of associated warehouse tasks

●

Determination of telegram traffic relating to individual HUs or warehouse tasks

●

Stopping or restarting of communication with regard to individual controls

●

Locking of communication points, segments, or resources

●

Resending of telegrams where necessary

●

Manual confirmation of warehouse tasks

You can call up logs for exceptions via the alert monitor [Extern]. The system generates these logs if communication with a PLC was interrupted and EWM initiated an automatic restart of the communication channel. You can link these exceptions with follow-on actions (such as notification of a control station [Extern]). A further evaluation allows the accessing of system logs [Extern] by the system administrator. An example of something that might be logged by the system is when a warehouse task pending transport was not sent to the PLC (due to insufficient capacity at the next communication point or due to a malfunction, for example). For more information, see MFS in the Warehouse Management Monitor [Seite 835] and MFS in the Alert Monitor [Seite 850].

For better understanding, the graphic below illustrates a possible automatic storage retrieval system in an example warehouse:

SAP Extended Warehouse Management (SAP EWM)

510

821

SAP Online Help

20.07.2007

Aisle 1

Aisle 2

Aisle 3

STC2

STC3

Storage bins in highrack storage area

STC1

Automatic storage retrieval

DTr

Distribution trolley

Putback withdrawal HU Transport off pick HU

I. point Pick HU

Pkg bin

Full pallets Pick HU GR

Clarification bin

GI

Empty pallets

This example warehouse consists of an automatic high-rack storage area with three aisles and automated putaway and removal. A distribution trolley links the putaway and picking area with the high-rack storage area.

From the MFS standpoint, this warehouse is operated with four controls. Three are for the stacker cranes (green) and one is for the distribution trolley and the conveyor lines of the preliminary (prestorage) zone (blue).

The warehouse has a single depth, the distribution trolley and stacker cranes each have just one load handling attachment (LHA).

The following graphic shows an example of the material flow in this example warehouse:

SAP Extended Warehouse Management (SAP EWM)

510

822

SAP Online Help

20.07.2007

STC2

STC3

4 6 2 3 STC1

DTr

Putback HU Transport off pick HU

I. Point

Pkg bin

6

1 GR

Full pallets Pick HU

Clarification bin

5 Empty pallets

GI

This example comprises the following processes:

1. Putaway 2. Removal from storage of full pallets 3. Supplying the picking bin 4. Putback 5. Conveying off the pick HU 6. Diversion to clarification bin

SAP Extended Warehouse Management (SAP EWM)

510

823

SAP Online Help

20.07.2007

Structure of the MFS In the MFS, a conveyor system is mapped via the following components:

●

PLC [Seite 825]

●

Communication channel [Seite 826]

●

Communication point [Seite 827]

●

Conveyor segment [Seite 828]

●

Resources [Seite 829]

The MFS controls the flow of materials within a plant by means of warehouse tasks at one or more PLCs. The PLC is linked to the MFS through one or more communication channels. An EWM warehouse task is subdivided into individual stages within the material flow. The start and end points of these stages are termed communication points. The telegram communication between the MFS and the PLC takes place there. The PLC regulates the necessary steps between two communication points itself. You set up communication points only at those locations at which decisions are necessary from the subordinate view, that is, which cannot or should not be made by the PLC itself. The connection between two communication points is termed the conveyor segment. If a vehicle whose movements are to be controlled by EWM is used for transportation from communication point to communication point or from/to storage bins, it is mapped in the MFS as a resource. For stacker cranes, the MFS contains a strategy for reducing the empty traveling path (Interleaving [Extern]).

SAP Extended Warehouse Management (SAP EWM)

510

824

SAP Online Help

20.07.2007

Programmable Logic Controller (PLC) Definition Underlying realtime system controlling the physical transportation of HUs on conveyor systems and their components.

Use The PLC evaluates signals from the connected automatic storage retrieval/conveyor system or other controls and activates or deactivates motors, appliances, sensors, readers, etc. Each control that is to communicate with the EWM system must be defined as a PLC. In larger installations, head controls [Extern] may be in use, which for their part regulate local controls [Extern]. The EWM system communicates with the head controls only. In EWM, you therefore define just the head controls. At least one communication channel [Seite 826] must be defined for each PLC.

SAP Extended Warehouse Management (SAP EWM)

510

825

SAP Online Help

20.07.2007

Communication Channel Definition Connection for transmission of messages between MFS and a control facility, defined by an IP address and a port.

Use To facilitate communication between MFS and a PLC, you must define a communication channel for this PLC. In the process, you define certain properties, such as the length of the messages and whether telegram confirmations are to be used. Via the application menu, you also make the settings for the IP address and port via which the PLC can be reached. You can use several channels to communicate with the same PLC. Each of these must use a separate port. You can specify that certain telegrams are to be sent via a particular port and other messages via a different one. Messages of a communication channel are communicated sequentially. This means that the system does not send message 2 until an acknowledgment of receipt has been received for message 1. As a rule, one communication channel per control is sufficient. However, communication can be accelerated by using a second communication channel (and perhaps others).

Ensure that you parallelize only those messages that may overtake each other if necessary. There may be undesired consequences, for example, if transportation receipts and logon telegrams are distributed among different channels. In cases of malfunction on one channel, they may not be processed in the intended sequence. For more information, see the IMG for EWM under Material Flow System (MFS) → Master Data → Communication Channel.

Example You specify that MFS is to communicate with the three stacker cranes in your warehouse via a separate channel for each one. With regard to the prestorage area, you expect a higher incidence of telegrams. You there fore define 2 channels (port 1 and port 2) for the responsible PLC. All HU-related telegrams are to pass along channel 1, whereas channel 2 is for all status telegrams (malfunction reports for communication points and segments). You therefore agree with the person responsible for the PLC that status telegrams are to be transmitted via port 2 and specify in EWM that telegram type STAR (status request from EWM to MFS) is to be routed via channel 2.

SAP Extended Warehouse Management (SAP EWM)

510

826

SAP Online Help

20.07.2007

Communication Point Definition Point in the automatic storage retrieval system at which EWM and the programmable logic controller (PLC) [Extern] exchange information (such as availability status, starting or destination point of a warehouse task, or scanner point).

Use A communication point is always assigned to one PLC only. EWM always also maps a communication point as a storage bin and, within layout-oriented storage control [Seite 340], as a storage group. Each communication point belongs to a certain communication point type. In this way, you can define a communication point type for identification points (points for storage bin assignment) or one for scanner communication points. As well the telegram type, the communication point type influences the MFS action that the system triggers for this communication point. A key property of communication points is their capacity. The capacity is expressed by the number of HUs permitted simultaneously at the communication point. In this connection, the program also takes incoming or outgoing HUs into account. A further important property is the availability status. You can lock a communication point either using the PLC or - via the warehouse management monitor - using the warehouse activity monitor [Extern].

Example Each communication point type can have its own flow logic. In a typical communication process, the conveyor system moves a handling unit (HU) to a scanner, for instance. You have defined this point as a communication point (for example, CP01) of the type I. Point in the MFS. The PLC now sends the data read by the scanner (HU number) to EWM together with the name of the communication point. EWM triggers the action (search for storage bin) defined for this telegram type (scanner telegram) and this communication point type (identification point), determines the next interim destination on the way to the storage bin, and then sends an appropriate telegram to the PLC (transport HU to next communication point “CP02"). The PLC causes the HU to be transported to the desired communication point via the conveyor system. When the HU arrives at this point, the PLC sends a new telegram (Logon at CP02) For this communication point you have set the type simple communication point. You have also specified that in the case of logons at simple communication points, a function module that reposts the HU at the new point and determines the next destination on the way to the final storage bin is to be invoked. If the next communication point has no capacity or an exception has been set at it, the warehouse task for the PLC is returned to EWM.

SAP Extended Warehouse Management (SAP EWM)

510

827

SAP Online Help

20.07.2007

Conveyor Segment Definition Leg between two communication points [Seite 827].

Use Conveyor segments physically transport handling units (HUs) from one communication point to the next. You can define a capacity limit for conveyor segments too. As in the case of communication points, the capacity relates to the number of HUs that can simultaneously be transported via the relevant conveyor segment. If the capacity of a conveyor segment is fully utilized, EWM holds back further orders for this segment. You assign conveyor segments to your start and end points in layout-oriented storage control [Seite 340]. You can combine different conveyor segments to form a conveyor segment group by conveyor segment group type (such as status). Thus, for example, you can assign an exception to the entire conveyor segment group instead of to individual conveyor segments in the case of a malfunction report; the system then holds back orders for these conveyor segments. You only need to define conveyor segments if you want to check their status (readiness, capacity) in EWM. In many cases, it will suffice to record capacity and status at communication points.

Example You have the following legs for a particular route in the warehouse: A Æ B Æ CÆ Destination You are awaiting status messages from the PLC for the segment between A and B. Likewise for the leg between B and C. Furthermore, not more than 3 orders are to be sent to the PLC simultaneously in this segment.

You define 2 conveyor segments, AB and BC. You enter the capacity 3 for BC.

In layout-oriented storage control, you define the interim destination B for the leg from A to the destination and assign the segment AB to this entry. You define the interim destination C for the leg from B to the destination and assign the segment BC to this entry. The MFS can now take any malfunctions in the segments AB and BC into account (in addition to the status of the affected communication points). It can also take account of the capacity limit in the segment BC.

SAP Extended Warehouse Management (SAP EWM)

510

828

SAP Online Help

20.07.2007

Resource Definition Object that performs a warehouse task. In the MFS, a vehicle that transports an HU from one communication point (or storage bin) to another. A resource moves to the pickup point in an empty state, takes on the load, and then discharges the latter at its destination. To achieve a reduction in empty travel paths, you must optimize the sequence of the orders.

EWM contains an interleaving strategy for stacker cranes with: ●

Just one load handling attachment

●

Putaway and removal bin at the same end of the aisle

EWM does not contain an empty-traveling-path strategy for distribution trolleys.

Use To optimize the movements of stacker cranes from within EWM, the stacker cranes must be mapped in EWM as resources. Conveyor lines are not mapped as resources. It is not necessary to define a distribution trolley that the programmable logic controller optimizes using a separate order buffer as a resource in SAP EWM either. It is sufficient to define the communication points served by the distribution trolley. You predefine resource types in Customizing (for example, STC). For more information, refer to the Implementation Guide (IMG) for EWM under Material Flow System (MFS) → Master Data → Define MFS Resources. You create resources (from STC1 to STCn) via the application menu. To do so, starting from the SAP Easy Access screen, choose Material Flow System (MFS) → Maintain MFS Resource. You need several resource types only if the resources to be controlled differ in respect of the following questions: ●

Is the interleaving [Extern] strategy activated?

●

How large is the order buffer?

●

What is the step sequence for telegram communication with respect to an order?

If interleaving is activated, EWM assigns the resource alternately a putaway and a removal from storage in each case. Each putaway is followed by a removal from storage (where available and executable). Conversely, each removal from storage is followed by a putaway. In the process, the system considers a pool of orders in each case. The basis for this is the latest start date/time (LSD/T). Orders whose LSD/T has been reached or will be reached within a definable period count as equal in terms of interleaving. The time interval is subdivided into a grid (for example into full hours). You define this grid in Customizing. For more information, see the IMG for EWM under Resource Management → Define Modes.

For more information on the general use of resources in EWM, see Resource [Seite 752].

SAP Extended Warehouse Management (SAP EWM)

510

829

SAP Online Help

20.07.2007

Set Up the Material Flow System Use To be able to connect up a programmable logic controller [Seite 825] (PLC) to Extended Warehouse Management (EWM), you must make the following settings.

Procedure Definieren ...

Customizing Settings: 1. Define PLC interface types. PLC interface types facilitate the settings for controls of a similar nature (for example, several stacker cranes with an identical interface). For more information, see the Implementation Guide (IMG) for EWM under Master Data → Material Flow System (MFS) → Master Data → Define PLC Interface Type. 2. Define a PLC in EWM for each real PLC with which EWM is to communicate. For more information, see the IMG for EWM under Material Flow System (MFS) → Master Data → Define Programmable Logic Controller (PLC). 3. Define one or more communication channels [Seite 826] for each PLC. For more information, see the IMG for EWM under Material Flow System (MFS) → Master Data → Communication Channel → Define Communication Channel. 4. Define communication point types. Consider whether you need a special processing for different communication points when telegrams of a certain type arrive. For more information, see the IMG for EWM under Material Flow System (MFS) → Master Data → Define Communication Point Types. 5. Define communication points [Seite 827]. Each point in the system that is not a final storage bin and which EWM is to take into account as an interim step must be a communication point. For more information, see the IMG for EWM under Material Flow System (MFS) → Master Data → Define Communication Point. 6. Define communication point dependencies if you want to limit the capacity of communication points in EWM or record the status at communication points in EWM. In doing so, you define which other communication points are checked by EWM with regard to HUs waiting there if a communication point is relieved or its status changes to "Ready". For more information, see the IMG for EWM under Material Flow System (MFS) → Storage Control → Define Communication Point Dependencies. 7. Define conveyor segments [Seite 828] if you want to check their status or capacity in EWM. For more information, see the IMG for EWM under Material Flow System (MFS) → Master Data → Define Conveyor Segment. 8. Define conveyor segment group types if you use conveyor segments and want to treat them jointly with regard to their status, for example. For more information, see the IMG for EWM under Material Flow System (MFS) → Master Data → Define Conveyor Segment Group Type. 9. Define conveyor segment groups if you want to treat conveyor segments jointly. For more information, see the IMG for EWM under Material Flow System (MFS) → Master Data → Define Conveyor Segment Groups.

SAP Extended Warehouse Management (SAP EWM)

510

830

SAP Online Help

20.07.2007

10. Then assign the conveyor segments to the conveyor segment groups. For more information, see the IMG for EWM under Material Flow System (MFS) → Master Data → Assign Conveyor Segments for Conveyor Segment Groups. 11. Flag the storage types that represent the warehouse regulated by the controls as MFSrelevant. Two storage type roles are available: 12. Prestorage area: H Material Flow Control for Automatic Storage Retrieval 13. High-rack storage area: J Automatic Warehouse (Driven by MFS). For more information, see the IMG for EWM under Master Data → Define Storage Type. 14. Define storage groups for layout-oriented storage control. The storage control allows you to group together storage bins with regard to route determination. This is done by means of storage groups. For more information, see the IMG for EWM under Material Flow System (MFS) → Storage Control → Define Storage Groups for Layout-Oriented Storage Control. 15. Define interim destinations for the transportation of HUs within your warehouse. You do this according to the principle: from A to Z via B, from B to Z via C. This point represents the core of your Customizing activities. You can specify source and destination either roughly (storage type only) or finely (with storage group). It is also possible to entirely do without one of the two. For example, "everything from aisle 1 irrespective of final destination - via the intermediate location CP13" (stock removal station of aisle 1). You can also specify different paths for full, partly full, or empty HUs. For more information, see the IMG for EWM under Material Flow System (MFS) → Storage Control → Define Layout-Oriented Storage Control. 16. Define suitable activity areas. You use activity areas to control the assignment of warehouse tasks to queues. The controls defined in each case process the queues. For more information, see the IMG for EWM under Master Data → Activity Areas → Activities. 17. Define an MFS queue for each PLC. For more information, see the IMG for EWM under Material Flow System (MFS) → Master Data → Define MFS Queue. 18. Define a resource category for each resource type used. For more information, see the IMG for EWM under Material Flow System (MFS) → Master Data → Define MFS Resource Category. 19. Define abbreviations for MFS actions. Define function modules that the system is to invoke in the case of these actions. For more information, see the IMG for EWM under Material Flow System (MFS) → Telegram Processing → Define MFS Actions. 20. Clarify the telegram structures (record structure, telegram types) with the person responsible for the PLC and create the corresponding record structures in the ABAP dictionary. You can use the Object Navigator of the ABAP Workbench for this purpose, for example. 21. Define which telegram IDs the PLC expects or uses for the intended message types and which record structures it uses in each case. For more information, see the IMG for EWM under Interfaces → Material Flow System (MFS) → Telegram Processing → Define Telegram Structure. 22. Define which action modules are to be invoked for which PLC telegrams. For more information, see the IMG for EWM under Material Flow System (MFS) → Telegram Structure → Find MFS Actions.

SAP Extended Warehouse Management (SAP EWM)

510

831

SAP Online Help

20.07.2007

23. Define the required exceptions. For more information, see the IMG for EWM under Material Flow System (MFS) → Exception Handling → EWM Exceptions. 24. Assign PLC errors to the relevant telegram errors. For more information, see the IMG for EWM under Material Flow System (MFS) → Exception Handling → Assign Telegram Errors to PLC Errors. System Settings 1. Create storage bins for the communication points and assign these to the communication points. In doing so, ensure that the storage bins each have the correct storage group. The system determines the storage group via the interim storage bins. On the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Product → Material Flow System (MFS) → Maintain Communication Points. 2. Define sorting rules for the new storage bins. The system assigns warehouse tasks to warehouse orders. In MFS, this is always a 1:1 assignment. Nevertheless, an activityrelated sort sequence is necessary for data-technical reasons. On the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Storage Bin → Sort Storage Bins. 3. Create a resource for each stacker crane and assign a queue to the resource. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Material Flow System (MFS) → Maintain MFS Resource. 4. Create a new RFC destination (TCP/IP connection). Define a program ID. You must set this in the external communication layer. The communication layer registers itself in the SAP system under this name. You can then invoke the communication layer from EWM. On the SAP Easy Access screen, choose Tools → ALE → ALE Administration → Runtime Settings→ Maintain RFC Destination. 5. Specify for each PLC whether you want to use the SAP communication layer SAP XMII MDS for EWM or a different communication layer. Specify the name of the RFC destination and, where appropriate, the functions to be invoked in the external communication layer. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Material Flow System (MFS) → Maintain Programmable Logic Controller. 6. Set the IP address and port of the communication channels. The EWM system passes on these parameters to the external communication layer when the channel is opened. The communication layer is then in this respect maintenance-free. On the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Material Flow System (MFS) ### Maintain Communication Channel. 7. Create a new TCP/IP connection. Enter a program ID. The external communication layer must use this to register itself in the SAP system. On the SAP Easy Access screen, choose Tools → ALE → ALE Administration → Runtime Settings→ Maintain RFC Destination. 8. Start the communication channels. On the SAP Easy Access screen, choose Extended Warehouse Management → Monitoring → Warehouse Management Monitor → Material Flow System → Communication Channel.

Result The material flow system is configured. SAP EWM can communicate warehouse tasks affecting the area of responsibility of the defined PLC to the latter and in this way control the relevant area in the warehouse without operator intervention.

SAP Extended Warehouse Management (SAP EWM)

510

832

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

833

SAP Online Help

20.07.2007

Repeating or Resending an Acknowledged Telegram Use EWM sends telegrams automatically as soon and as long as the relevant communication channel is synchronized. Synchronization means that after a connection has been established by EWM the PLC has been given the opportunity to send all messages that accumulated during the period of disconnection. The PLC transmission buffer is thus empty. The PLC sends an acknowledgment of receipt for the telegram received, whereupon EWM posts it as sent. If there is no acknowledgment, EWM repeats the telegram (after a period of time configurable at the channel, such as 5 seconds). Unacknowledged telegrams are thus automatically repeated by EWM. In certain cases it is necessary to manually resend an already acknowledged telegram (if the PLC was subject to malfunction status following an error and unintentionally deleted the telegram while the problem was being manually rectified, for example). In this case, you can resend the telegram from within the telegram log. For test purposes, you also have the option of first manipulating the telegram that is to be sent (meaning simulating a telegram that cannot be produced or is difficult to produce in the intended way in order to test it). In the process, you can change all the fields provided as standard. For example, you can enter a different HU number or a different communication point as the destination. Use this function during the test phase only - not when you go live. You can ensure this by assigning the appropriate authorizations.

Prerequisites You have invoked the warehouse management monitor via the following initial view: SAP Easy Access → Extended Warehouse Management → Monitoring → Warehouse Management Monitor.

Activities Select the desired telegram and choose Other Methods → Tel. Repeat Send. Decide whether the system is to pull a new run number for the telegram or use the original one. An already acknowledged run number may be discarded by the PLC as a repetition (that is, acknowledged but not processed). The system then resends the telegram.

SAP Extended Warehouse Management (SAP EWM)

510

834

SAP Online Help

20.07.2007

MFS in the Warehouse Management Monitor Use The warehouse management monitor provides you with the following options: ●

Invocation of information on the system status, pending tasks, and the current occupancy of communication points and resources

●

Evaluation and tracking of shipments and telegram traffic

●

Starting and stopping the communication channels

●

Targeted intervention in the event of malfunctions

Features You can track the following objects in the warehouse management monitor: ●

Communication channel As a rule, the communication channels will have been started. In the warehouse management monitor, you can stop or restart individual connections.

●

Communication point You can display a list of the communication points with their current status. Various sort and selection options are available (for example, you can display malfunctioning communication points). You can also lock communication points.

●

Telegram You can display logs of PLC telegrams received and sent. Here, too, you have various select options such as by time of transmission. This overview is an important analysis instrument in the case of malfunctions. From here, you can branch directly to the affected warehouse tasks.

●

Warehouse task You can call up a list of the current warehouse tasks and a warehouse task history. In the case of malfunctions, you can cancel or manually confirm warehouse tasks and you can branch directly to the associated telegrams and to the creation log for the warehouse task.

●

Handling units (HUs) You can invoke a list of the HUs currently located within the automatic storage retrieval system. You see their current location, the status of the associated warehouse tasks, and the related telegrams sent. Furthermore, you can divert HUs in the case of errors.

●

Conveyor segment, conveyor segment group You can invoke an overview of the status of the conveyor segments or segment groups. You can also manually lock individual segments or entire segment groups.

●

Resource You can call up a status overview or manually lock the resource.

●

Telegram buffer Telegrams received that could not be processed remain in the inbound buffer with error flags. Where appropriate, you can manually correct them and flag them for posting.

SAP Extended Warehouse Management (SAP EWM)

510

835

SAP Online Help

20.07.2007

Telegrams due to be transmitted or which have been transmitted but not yet acknowledged by the PLC are visible in the outbound buffer. The two buffers should always be empty.

Prerequisites You have defined the storage type role H Material Flow Control or J Automatic Warehouse (Driven by MFS). For more information, refer to the Implementation Guide (IMG) for EWM under Master Data → Storage Type. The selection of the MFS-relevant HUs and the MFS-relevant warehouse tasks is based on the storage type role of the affected storage types. You define these storage types in Customizing for EWM.

Activities From the warehouse management monitor, you can carry out the following activities for each node:

Node

Activities

Communication channel

Start or stop communication channel. Reset run number for received or sent telegrams.

Communication point

Define exception, query status, trigger processing.

Telegram

Send repeat telegram, simulate telegram.

Warehouse task

Simulate warehouse task, display warehouse task log, split off from warehouse task, assign warehouse task, revoke warehouse task assignment, confirm in foreground, confirm in background, reprint warehouse task, cancel warehouse task, define exception.

HU

Set MFS error; trigger processing.

Conveyor segment group

Define exception

Conveyor segment

Define exception

Resource

Define exception, query status, trigger processing.

Telegram buffer

Process or delete telegram.

SAP Extended Warehouse Management (SAP EWM)

510

836

SAP Online Help

20.07.2007

Analyze Logs Use In the warehouse management monitor, you can invoke the log of incoming and outgoing telegrams to view details and check whether any problems have arisen. Here you can call up and view the exact times of transmission and receipt, as well as the sender and recipient of the telegram. Furthermore, you an search for special objects such as the HU number, communication point, telegram run number, or telegrams with a certain error code. The log contains the following data (where available): ●

PLC

●

Communication channel

●

Communication point

●

Date

●

Handshake [Extern]

●

Handling unit

●

Sender

●

Recipient

●

Source

●

Destination

●

Telegram type

●

Run number

●

Warehouse task number

You may be able to obtain more exact information In the alert monitor [Seite 850]. Consider the fact that the logs may become extremely voluminous, depending on the extent of the telegram traffic. Evaluation queries pertaining to individual attributes may therefore take increasingly longer over time. You should therefore archive or delete older logs on a regular basis. To do so, starting from the SAP Easy Access screen, choose Master Data → Material Flow System (MFS) → Delete Telegram Log.

Prerequisites You have activated the logging function for each PLC. To do so, starting from the SAP Easy Access screen, choose Master Data → Material Flow System (MFS) → Maintain Programmable Logic Controller and set the Logging indicator.

SAP Extended Warehouse Management (SAP EWM)

510

837

SAP Online Help

20.07.2007

MFS in the Easy Graphics Framework Use You can call up read-at-a-glance information on the status of certain MFS-relevant objects via the Easy Graphics Framework [Seite 68]. If the various elements within the material flow are being used without any hitches, the system displays a green traffic light. As soon as a malfunction occurs, the system displays a red traffic light.

Features You can call up the following objects in the Easy Graphics Framework: •

Status of communication channel ○

•

Status of communication layer ○

•

Red: Exception; Green: No exception

Status of outgoing telegrams ○

•

Red: Not running; Green: Running

Status of MFS resource ○

•

Red: Cannot be reached; Green: Can be reached; Grey: Communication layer cannot be checked; status unknown.

Status of process for telegram repetition ○

•

Red: Communication channel has been stopped; Green: Communication channel running; Yellow: Synchronization running

Red: At least one outgoing telegram has not been acknowledged in good time; Green: All telegrams sent in timely manner

Status of incoming telegrams ○

Red: Telegram has run into an error upon receipt (for example, a warehouse task is to be confirmed for an HU that does not exist in EWM); Green: All telegrams have been received without errors

For more detailed information on the status of the individual objects, see Warehouse Management Monitor [Seite 835].

SAP Extended Warehouse Management (SAP EWM)

510

838

SAP Online Help

20.07.2007

Status Management Use In MFS, you can manually change the status of the following objects: •

Conveyor segments

•

Conveyor segment groups

•

Resource

•

Communication point

•

Communication channel

This makes sense, for example, if you want to lock objects due to maintenance work or because of a malfunction. Each time the status of an object changes, an exception handling [Seite 841] process is triggered. You can set an appropriate exception code in the warehouse management monitor [Seite 835].

Object Conveyor segment

Conveyor segment group

Resource

Communication point

Status

Trigger

●

Locked (user)

●

●

Malfunction (PLC)

User manually sets a lock in the warehouse management monitor

●

●

Telegram from the PLC

Ready

●

Locked (user)

●

●

Malfunction (PLC)

User manually sets a lock in the warehouse management monitor

●

●

Telegram from the PLC

Ready

●

Action relates to all segments contained therein

●

User manually sets a lock in the warehouse management monitor

●

Telegram from the PLC

●

User manually sets a lock in the warehouse management monitor

●

Telegram from the PLC

●

Locked (user)

●

Malfunction (PLC)

●

Ready

●

Locked (user)

●

Malfunction (PLC)

●

Ready

●

SAP Extended Warehouse Management (SAP EWM)

510

839

SAP Online Help

Communication channel

20.07.2007

●

Active

●

Inactive

SAP Extended Warehouse Management (SAP EWM)

User starts or stops the channels manually in the warehouse management monitor

510

840

SAP Online Help

20.07.2007

Exception Handling Use You can use exception handling to control the system's reaction to error codes that the PLC reports in telegrams. Furthermore, you can specify the error codes that EWM can set in the confirmation telegram to the PLC in the case of communication errors.

Features You can define two types of exception in the PLC: 1. Exceptions that the PLC reports in the telegram. Assign an exception to each possible PLC error code in Customizing. For more information, see the Implementation Guide (IMG) for EWM under Material Flow System (MFS) → EWM Exceptions → Define EWM Exception for PLC Errors. 2. Exceptions that the system sets due to an internally recognized error situation. Here it defines an internal exception. Because this error situation may not be self-explanatory to the user, it must be linked to an external exception in Customizing. This external exception contains a text and possibly a setting for reacting to the error. For more information, refer to the IMG for EWM under Cross-Process Settings → Exception Handling → Assign Internal Exception Codes to Exception Codes.

SAP Extended Warehouse Management (SAP EWM)

510

841

SAP Online Help

20.07.2007

Business Contexts To group exceptions and define their validity, you assign them to a business context in each case. The business context defines the circumstances in which the exception can be set. Each exception is valid in one certain business context only. You should not use the exception Communication point locked on a communication channel, for example, or HU errors on a storage bin.

The execution step is a further characteristic enabling you to regulate the validity of exceptions. In the MFS, the following execution steps are defined: ●

A0 - Processing in background (for example, inbound telegram)

●

A1 - Processing at desktop

The execution step A0 is always set if processing triggered by a PLC telegram results in the occurrence of an exception. The execution step A1 applies to events triggered by an operator action (for example, at the warehouse management monitor). If you want it to be possible for an exception to be set by an operator, you must define it for the execution step A1. If the exception (and the follow-on processing linked to it) is to have validity in the case of an automatic event, you must define it for the execution step A0.

The following table contains situations in which errors are liable to occur (for which you should therefore define exceptions) and the context used by the program in each case.

Context

Description

MF1

MFS - Communication channel

Situation in which the system sets the context ●

If the confirmation telegram contains a communication error

●

If it is not possible to send a telegram The system chooses the exception maintained on the communication channel.

●

When the status on the communication channel is set or released. At the time of status setting, the system chooses the exception maintained on the communication channel. At the time of status release, the system chooses the exception assigned to the internal exception MFS6.

MF2

MFS - Transportation

SAP Extended Warehouse Management (SAP EWM)

●

When the status on the

510

842

SAP Online Help

20.07.2007 conveyor segment is set or released. At the time of status setting, the system chooses the exception determined on the basis of the telegram error or entered by the user. At the time of status release, the system chooses the exception assigned to the internal exception MFS2.

segment/group

•

When the status on the conveyor segment group is set or released. At the time of status setting, the system chooses the exception determined on the basis of the telegram error or entered by the user. At the time of status release, the system chooses the exception assigned to the internal exception MFS2.

MF3

MFS - Telegram

●

If an error code is detected in the telegram in the action modules The system uses the exception that it determined on the basis of the telegram error.

●

If an error telegram is to be sent due to a semantic or syntactical error in the telegram received. The system determines a telegram error via the error type (for example, Start sequence incorrect, Sequence number incorrect) and the exception via the telegram error.

MF4

MFS - Resource

●

If the system recognizes the internal exception MFS7 Unknown HU reported

●

When the status on the resource is set or released. At the time of status setting, the system chooses the exception determined on the basis of the telegram error or entered by the user. At the time of status release, the system chooses the exception assigned to the internal exception MFS4.

MF5

MFS - Communication point

SAP Extended Warehouse Management (SAP EWM)

●

When the status on the communication point is set or released.

510

843

SAP Online Help

20.07.2007

At the time of status setting, the system chooses the exception determined on the basis of the telegram error or entered by the user. At the time of status release, the system chooses the exception assigned to the internal exception MFS5. Reading of Table: Example: If you define an exception that is to lay down a reaction to an error code in an incoming confirmation, you must use the context MF1 and execution step A0 for this purpose. Otherwise, the EWM system is not able to find the exception and the desired reaction cannot occur.

For the business context MF3, only the execution step A0 makes sense. All other business contexts are assigned to the execution steps A0 or A1.

SAP Extended Warehouse Management (SAP EWM)

510

844

SAP Online Help

20.07.2007

Internal Exceptions The system sets an internal exception if an error occurs (if a scanner has reported an unknown HU, for example). The system sets the following exceptions internally. You must supplement these internal exceptions by external ones in Customizing. The external exception then specifies: ●

The wording of the error message that appears in the alert monitor

●

How the system reacts (for example, diversion of HU to clarification bin)

●

Whether a further follow-on action takes place (for instance, notification of a remote control station via mail or text message)

Internal exception

Error situation

Context/step

Use

MFS1

The PLC confirms a warehouse task: The destination does not correspond to the expected position. (There is no open warehouse task for the relevant communication point.)

MF3 / A0

The system reposts the HU to the point reported by the PLC. If you want to log this variance, assign an external exception (such as MLOC) to the internal exception MFS1 and activate the follow-on action Alert for it. If you want such "strays" to be diverted to the clarification bin, assign the internal process code CRCL to the external exception.

MFS2

Release conveyor segment: The PLC reports a conveyor segment or conveyor segment group as ready again.

MF2 / A0

If you want this event to be logged in the alert monitor, assign an external exception to this internal exception, define the text

Conveyor segment ready for

This exception facilitates the option of logging the event and triggering possible follow-on actions. MFS3

- Not used -

MFS4

Release resource: The PLC reports that a resource is ready again.

the former, and activate the follow-on action Alert.

MF4 / A0

This exception facilitates the option of logging the event and triggering possible follow-on actions. MFS5

Release communication point: The PLC reports that

If you want this event to be logged in the alert monitor, assign an external exception to the internal exception, define the text

Resource ready for the former, and activate the follow-on action Alert. MF5 / A0

SAP Extended Warehouse Management (SAP EWM)

If you want this event to be logged in the alert monitor, assign an 510

845

SAP Online Help

20.07.2007 a communication point is ready again.

external exception to the internal exception, define the text

This exception facilitates the option of logging the event and triggering possible follow-on actions. MFS6

Release communication channel

Communication point ready for the former, and activate the follow-on action Alert. MF1 / A0

This exception facilitates the option of logging the event and triggering possible follow-on actions.

If you want this event to be logged in the alert monitor, assign an external exception to the internal exception, define the text

Communication channel ready for the former, and activate the follow-on action Alert.

MFS7

Unknown HU reported: The PLC has reported an HU that is unknown to the EWM system.

MF3 / A0

SAP Extended Warehouse Management (SAP EWM)

If you want to have the unknown HU automatically diverted, define the external exception - Unknown HU reported. Assign the internal process code HUNO to this exception. The system then creates a new empty HU and diverts it to the clarification bin.

510

846

SAP Online Help

20.07.2007

Internal Process Codes You can use internal process codes to define how the system is to react to exceptions. Process code

Description

Context/step

Use

BOVF

The PLC reports a telegram buffer overflow.

MF1 / A0

The EWM system ignores the confirmation telegram according to the wait time that has been set. As a result, the telegram is automatically repeated.

COMM

Set status on communication channel.

MF1 / A0

The EWM system does not trigger any additional action. The status is set on the communication channel. You can utilize the options for exception handling (for example, alert or workflow).

REST

Restart of communication channel.

MF1 / A0

The EWM system stops the affected communication channel and restarts it.

SEQW

The PLC rejects the run number of the telegram sent by the EWM system. (For example, because the PLC memory has been deleted and the PLC is therefore no longer able to decide whether or not the run number received is valid.).

MF1 / A0

The EWM system resets the run number and resends the current telegram with the sequence number 0.

Move HU to clarification storage bin

MF2 / A0

CRCL

The sequence number 0 counts as a reset and is always accepted by the recipient.

MF2 / A1 MF3 / A0 MF5 / A0 MF5 / A1

NSND

A communication point or a segment is malfunctioning, locked, or has no free capacity. You

MF2 / A0 MF2 / A1 MF4 / A0

SAP Extended Warehouse Management (SAP EWM)

The EWM system updates the exception on the HU. It cancels all open warehouse tasks for the HU and creates a new warehouse task for the HU for the clarification bin. The EWM system creates the warehouse task for the HU but does not send it.

510

847

SAP Online Help

20.07.2007 nevertheless want to create a warehouse task, which you do not, however, want to send to the PLC.

MF4 / A1

A communication point or a segment is malfunctioning, locked, or has no free capacity. You therefore do not want to generate a warehouse task.

MF2 / A0

BINE

A stacker crane reports that the storage bin passed on as the From bin in a warehouse task is physically empty.

MF3 / A0

The EWM system cancels all warehouse tasks for the HU and attempts to create new warehouse tasks.

BINO

A stacker crane reports that the storage bin passed on as the To bin in a warehouse task is physically occupied.

MF3 / A0

The EWM system attempts to determine a new, empty storage bin. As a result, the current warehouse task is changed and the telegram with the new data immediately sent.

HUNO

a) The PLC reports that an unidentifiable HU has passed a scanner.

MF3 / A0

The EWM system creates a new, empty HU and conveys it to the clearing bin.

MF3 / A0

The system changes the indicator WT to Subsystem in the warehouse task from 1 - Cancellation Request Relevant to External System to X WT Sent to External System.

STAY

MF5 / A0 MF5 / A1

MF2 / A1 MF4 / A0

The EWM system does not create a warehouse task for the HU.

MF4 / A1 MF5 / A0 MF5 / A1

b) The PLC reports an HU that is not known in EWM. NOCN

Cancellation not possible

Example using the internal process code HUNO: The PLC reports the error NOREAD (with error code 10, for example) in the telegram. You translate this error code into the exception MUFO in Customizing. You define the error text Noread at scanner for the exception MUFO.

SAP Extended Warehouse Management (SAP EWM)

510

848

SAP Online Help

20.07.2007

The follow-on action Alert leads to an entry "Noread at scanner xxx“ in the alert monitor. The internal process code HUNO causes EWM to draw a new HU number, internally create a new HU, and transfer the HU to the clarification bin.

SAP Extended Warehouse Management (SAP EWM)

510

849

SAP Online Help

20.07.2007

MFS in the Alert Monitor. Use You can use the alert monitor to keep track of whether any errors have occurred within the material flow and, if so, which. The system displays the priority of the error, the time at which it occurred, and a description. It displays further information (if such information exists), such as the sender, recipient, source, or destination, from the telegram that caused the error. For more information, see Alert Monitor [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

850

SAP Online Help

20.07.2007

Quality Management (QM) Purpose QM uses the Quality Inspection Engine [Seite 888] (QIE) to map inspection processes in Extended Warehouse Management (EWM). You can use QM to automatically or manually check whether delivered or putaway products satisfy your quality criteria. If you want to check products, packaging, or transports, you can perform the following inspections: ●

●

Inspections for the goods receipt process ○

Inspect the entire inbound delivery

○

Inspect the delivered handling units (HUs)

○

Count the delivered products

○

Inspect the delivered products for supplier inbound deliveries

○

Inspect the delivered products for customer returns

Inspections in the warehouse If, for example, you determine that one piece of a putaway product quantity is damaged, you can trigger a quality inspection manually.

●

Inspections for returns ○

In SAP Customer Relationship Management (SAP CRM), you can define parameters that influence the goods receipt and the quality inspection of returns in the warehouse.

○

Following the quality inspection, Extended Warehouse Management (EWM) sends the inspection outcomes to SAP CRM. SAP CRM evaluates the inspection outcomes. You can use this evaluation to trigger logistical follow-up actions, such as stock transfer or scrapping.

Prerequisites ●

You have made the settings for inspection document generation in Customizing. For more information, see Customizing Settings for QM in EWM [Seite 853].

●

You have created the necessary master data [Seite 855].

Aktffffff...

Process ...

1. For inbound deliveries, the system automatically generates an inspection document [Seite 869]. However, you can also create inspection documents manually, for checking handling units (HUs), for example. If the inspection object type [Extern] is active, the system looks for an inspection rule [Seite 901]. It can only generate inspection documents if you have created an inspection rule. If the system finds an inspection rule, it creates the inspection document. 2. You post the goods receipt. EWM releases the inspection document at the time of goods receipt or, in the case of partial goods receipt, at the time of the first goods receipt for the item. 3. EWM looks for a storage bin for the inspection quantity or, in the case of samples, for the sample quantity. For more information about putaway, see Putaway [Seite 300].

SAP Extended Warehouse Management (SAP EWM)

510

851

SAP Online Help

20.07.2007

○

If the sample is stock-relevant, such as a motor, EWM generates two warehouse tasks [Extern] (WTs). One of these is to transport the motor being checked to the work center, and the other is to put away the remaining quantity of the motors that are not being checked.

○

If the sample is not stock-relevant, such as a carton of milk from a large total quantity, then EWM only generates one warehouse task, to put away the total quantity.

4. You inspect the sample [Seite 925] or sample quantity. 5. You make a decision regarding the quality and follow-up process of the object checked in the inspection document by making an inspection decision [Seite 930] and selecting a decision code. Choosing a decision code is mandatory for inspection items but optionalfor samples. In addition, you can record a finding. 6. You may trigger follow-up actions [Seite 876], depending on the inspection decision. A follow-up action can in turn trigger a WT, such as scrapping.

Result You have performed a quality inspection after generating the inspection document. You have appraised the quality of the checked objects in the inspection decision. The inspection decision that has been met may have triggered follow-up actions, which decide how the checked objects are to be dealt with.

SAP Extended Warehouse Management (SAP EWM)

510

852

SAP Online Help

20.07.2007

Customizing Settings for QM in EWM Use The following describes Customizing settings in Extended Warehouse Management (EWM) that you must make for quality management (QM), to ensure a smooth implementation with the Quality Inspection Engine (QIE) and the ERP system. For more information about the individual activities, see the Implementation Guide (IMG) for EWM under Cross-Process Settings → Quality Management.

Activities Basic Settings for QM in EWM ...

1. Activate the required inspection object types [Seite 900], and assign them to properties. Examples of properties are warehouse number, product, owner, and supplier. To do this, in Customizing for EWM choose Cross-Process Settings → Quality Management → Basics → Activate Inspection Object Types Version. 2. Define the use and sequence of inspection properties [Extern] and activate the entry after completing the settings. To do this, in Customizing for EWM choose Cross-Process Settings → Quality Management → Basics → Maintain Inspection Object Types Version. 3. Activate the required inspection object types for your warehouse numbers, and assign sample types and items types, depending on the inspection object type and the required use. ○

If there are active inspection object versions, you have to activate the inspection object types being used for each warehouse number. Define warehouse number-specific parameters.

○

If you want to forward data from the quality inspection to an external system, specify the external system in which the inspection is to take place for each inspection object type and warehouse number. There you can use more extensive functions for planning and performing the inspection, such as planning characteristics.

○

Define the date/time of inspection document creation for inbound deliveries and returns, depending on whether you want to check HUs and whether you are documenting the arrival of goods in the yard [Seite 619]. For the process with HU inspection, this must be set to initial. For the process without HU inspection, you use the inspection document creation as a basis when activating the delivery.

To do this, in Customizing for EWM choose Cross-Process Settings → Quality Management → Basics → Warehouse-Dependent Activation of Inspection Object Type. 4. Define indexes for the search for inspection documents, samples and items. For each index, you define the properties that the index is to include. To do this, in Customizing for EWM choose Cross-Process Settings → Quality Management → Basics → Define Indexes for QIE Objects. 5. Define number ranges for inspection documents and samples/items. In Customizing for EWM, choose Cross-Process Settings → Quality Management → Settings for Inspection Rules → Define Number Ranges for Inspection Documents and Define Number Ranges for Samples and Items. 6. Define item types. If you are using samples [Seite 925], define sample types as well.

SAP Extended Warehouse Management (SAP EWM)

510

853

SAP Online Help

20.07.2007

In Customizing, choose Cross-Application Components → Quality Inspection Engine → Samples and Items → Define Sample Types and → Define Item Types. 7. Define finding types [Seite 927]. To do this, in Customizing for EWM choose Cross-Process Settings → Quality Management → Settings for Inspection Rules → Define Finding Types. 8. Define decision codes and follow-up actions. To do this, in Customizing for EWM choose Cross-Process Settings → Quality Management → Result → Define Decision Codes and Maintain Follow-Up Action.

Basic Settings for QM in the QIE 1. Define print control for printing inspection documents. In Customizing, choose Cross-Application Components → Quality Inspection Engine → Central Settings → Print Control → Check Settings in Post Processing Framework. 2. Connect the EWM system to the QIE. In Customizing, choose Cross-Application Components → Quality Inspection Engine → Central Settings → Communication with an External QM System → Define External QM Systems.

Basic Settings for QM in the ERP System 1. For checks that are triggered by an external system, SAP delivers the inspection lot origin 17. Select this inspection lot origin. In Customizing for the ERP system, choose Quality Management → Quality Inspection → Inspection Lot Creation → Maintain Inspection Lot Origins and Assign Inspection Types. 2. For samples that are created externally, SAP delivers sample type 10. Use this sample type in your inspection type. SAP delivers inspection type 17, which uses sample type 10. In Customizing for the ERP system, choose Quality Management → Quality Inspection → Sample Management → Define Physical Sample Types. 3. Activate the event type linkage [Extern]. In Customizing for the ERP system, choose Quality Management → Environment → Tools → Communication with Quality Inspection Engines → Archive Event Type Linkages for Confirmations. 4. Implement QPLEXT_COMM_TEC in the ERP system to switch to using background RFC as communication technology. 5. Perform standard Customizing for QM in SAP ERP. In Customizing for the ERP system, define the activities that are relevant for you. For more information about QM in the ERP system, see the SAP Library under SAP ERP Central Component → Logistics → Quality Management (QM).

SAP Extended Warehouse Management (SAP EWM)

510

854

SAP Online Help

20.07.2007

Master Data Use You use this function to manage master data that is required for quality management (QM).

Integration QM uses data from Extended Warehouse Management (EWM) and the Quality Inspection Engine (QIE), and makes this data available to you on the EWM user interfaces.

Prerequisites You have executed QM Customizing [Seite 853].

Features The following belong to master data relevant for QM in EWM: QM-Specific Master Data [Seite 856] Creation of Inspection Rule [Seite 857] Sample-Drawing Procedures [Seite 917] To define sample-drawing procedures, on the SAP Easy Access screen choose Extended Warehouse Management → Master Data → Quality Management → Maintain Sample-Drawing Procedure. Quality Level [Seite 912] Dynamic Modification [Seite 907]

SAP Extended Warehouse Management (SAP EWM)

510

855

SAP Online Help

20.07.2007

QM-Specific Master Data Use You can use this function to define quality inspection groups and quarantine periods. You define the quality inspection group through the product. This enables you to group products by QM criteria. If the products are different but the inspections and inspection conditions of these products are the same, this simplifies the definition of inspection rules for you. Assign the same quality inspection group to the products that you want to check using the same inspection rules. The quarantine period is the time in the corresponding time unit for which you have to store a product after production before you can ship it to the customer.

Integration QM-specific master data is a component of the inspection rule and can be included in the inspection rule findings.

Prerequisites To be able to use quality inspection groups, you have defined them in Customizing. To do this, in Customizing for EWM choose Cross-Process Settings → Quality Management → Settings for Inspection Rules → Define Quality Inspection Groups.

Example You define a quality inspection group 100% Metal and assign all metal products that you want to check 100% to this group. The group also has the same decisions and finding data as metals.

SAP Extended Warehouse Management (SAP EWM)

510

856

SAP Online Help

20.07.2007

Creation of Inspection Rule Use You use this function to define the inspection rules required by the system for creating inspection documents, under consideration of the dynamic modification criteria [Seite 913] you have defined. Inspection rules contain the following parameters: ●

Check criteria, such as material being checked, quality inspection group being checked, and supplier

●

Type of inspection (sample inspection and 100% inspection)

●

Possible decisions, findings, and follow-up actions

Inspection rules are dependent on the inspection object type, warehouse number, and version of the inspection object type. You can also use inspection rules to influence logistics management, by executing the following: ●

Defining the stock type of the stock that is to be checked and has been checked

●

Identifying the stock that is to be checked or is being checked

●

Transporting the stock being checked to special work centers

●

Transporting the checked stock to special areas, such as for scrapping or return delivery

Integration Depending on the inspection object type, you can use the following master data in the inspection rule: ●

Material master records

●

Business partners

●

Work center [Seite 35]

You can also include the following in inspection rules: ●

Sample procedures [Seite 904] You define a sample-drawing procedure comprising a sample-drawing unit [Seite 919] and sample-drawing instruction [Seite 920] in Customizing for the QIE. This enables you, for example, to define a sample-drawing instruction of type Container in such a way that you inspect ten pieces out of every HU or pallet of a goods receipt.

Prerequisites You have defined and sorted parameters for the inspection rule determination, and have activated them using Maintain Inspection Object Types Version. To do this, in Customizing for EWM choose Cross-Process Settings → Quality Management → Settings for Inspection Rules.

Features To define the inspection rules, you have the following options:

SAP Extended Warehouse Management (SAP EWM)

510

857

SAP Online Help

20.07.2007

●

You can define warehouse-specific and cross-warehouse inspection rules.

●

You can copy inspection rules to new inspection object type versions.

●

You can create, change and display inspection rules.

●

You can deactivate an inspection rule by choosing the inspection procedure No Check.

Inspection Procedure You can choose the 100% inspection or sample inspection as an inspection procedure.

EWM-Specific Arguments EWM-specific arguments of the inspection rule Argument of Inspection Rule

Definition

Inspection rule group

Short code with description for grouping inspection rules of the same type

Inspection duration

The system uses this entry to calculate the planned end time of the check using the WIP monitor, a special view in the warehouse management monitor [Seite 878]

Independent stock type

Defines the stock type in which you want to post the inspection stock

Process step

If storage control is not active, or if the delivery item is unpacked, you use the external process step (storage control) to define the inspection area in the warehouse.

EWM-specific arguments for samples Argument of Sample

Definition

Quality control

Destructive sample, relevance for follow-up action after completing inspection

Warehouse process type

Warehouse process type with which you want to move the sample. Use this argument with movement-relevant samples.

Movement-relevant

Indicator with which you define whether the sample quantity is moved in the warehouse and is trackable

Document link

You can connect documents from different applications, such as Microsoft Word or Microsoft Excel, to objects in the QIE.

Activities Define at least one inspection rule for each inspection object type that you want to use. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Master Data → Quality Management → Maintain Inspection Rule. Define inspection rules for the inspection object type for the various property values. This means, for example, that you define inspection rules for an owner, or for a combination of owner and product. You specify the inspection rule arguments for each inspection rule, namely the parameters for the checks being performed. .

SAP Extended Warehouse Management (SAP EWM)

510

858

SAP Online Help

20.07.2007

1. You only perform a product inspection. Assign an inspection procedure to define whether a check is to be performed. If a check is to be performed, you define whether it is to be a 100% inspection or a sample inspection. 2. Depending on the inspection procedure, you also specify a sample procedure or a sample-drawing procedure and dynamic modification rule, if required. 3. If required, you assign documents that contain the inspection instruction or product specifications, for example. When the system creates an inspection document based on the inspection rule, it passes the assigned documents on to the inspection document. 4. You specify a code group for the inspection document valuation. For HU inspections, counting, and returns, you also specify a code group for items. For inbound deliveries and warehouse-internal movements, specifying a code group is optional. 5. You specify an action profile of the Post Processing Framework [Extern] for printing documents belonging to the inspection document and sample-drawing instruction. 6. If you want the system to automatically create samples when creating an inspection document, specify a sample type, sample-drawing procedure, and a sample-drawing unit. 7. If you want to decide on the samples to be created separately, specify a decision code. 8. If you want to record defects and deviations, specify a finding type and a catalog filter for findings. Use the data that is offered for defects. For effort, the catalog filter corresponds to the defect group.

SAP Extended Warehouse Management (SAP EWM)

510

859

SAP Online Help

20.07.2007

Sample-Drawing Procedure Master data record that regulates how samples are taken and formed.

Structure You enter the following data in the sample-drawing procedure: •

You define the type of sample drawing. That is, you choose one of the following options: o

The samples are taken at predefined time intervals, for example, every five hours.

o

The samples are taken at predefined quantity intervals, for example, every 500 kg.

o

The samples are taken on a per container basis, for example, one sample for each pallet.

o

The samples are taken in accordance with the specifications that you defined in Customizing for the Quality Inspection Engine in the Business Add-In (BAdI) QIE Sample Calculation.

•

You define the sample-drawing units.

•

You define the sample-drawing instructions for the sample-drawing units.

Integration The sample-drawing procedure is a collection of sample-drawing units. The sample-drawing procedure itself does not contain any data for the sample drawing. You can define any number of sample-drawing units for a sample-drawing procedure. For every sample-drawing unit you can specify sample-drawing instructions for the following sample categories: •

Primary sample

•

Pooled sample

•

Reserve sample

Note the following: •

For reserve samples, you may only specify a maximum of one sample-drawing instruction.

•

If you specify more than one sample-drawing instruction for primary samples, you may not specify any sample-drawing instructions for pooled samples.

•

If you specify one or more sample-drawing instructions for pooled samples, you must specify exactly one sample-drawing instruction for primary samples. This sampledrawing instruction defines the primary samples that are mixed together to form the pooles samples.

You can specify the following sample-drawing instructions for one sample-drawing unit: Possible Number of Sample-Drawing Instructions for Each Sample Category (n = 1, 2, 3, ...)

SAP Extended Warehouse Management (SAP EWM)

510

860

SAP Online Help

20.07.2007

Primary sample

Pooled sample

Reserve sample

n

0

0

n

0

1

1

n

0

1

n

1

0

0

1

Note the following for the sample quantity that you specify in the sample-drawing instructions: •

You must either specify the sample quantity for none or for all of the sample drawing instructions for a sample-drawing unit.

•

If you specify more than one sample-drawing instruction for pooled samples or primary samples, all of these sample-drawing instructions must contain a sample quantity and these sample quantities must have the same unit.

If you specify sample-drawing instructions that do not adhere to these specifications, the system ignores these sample-drawing instructions and creates a primary sample that includes the whole sample quantity when the sample calculation for the inspection document is executed. If, when the system creates the inspection document based on the inspection rule, the system finds a sample-drawing procedure as well as a sampling procedure, it will initially only take the sample-drawing procedure into consideration. Only if the system cannot find all the data it requires in the sample-drawing procedure, will it take the sampling procedure into consideration.

SAP Extended Warehouse Management (SAP EWM)

510

861

SAP Online Help

20.07.2007

Quality Level Data record that the system automatically updates at the time of dynamic modification (at inspection document creation or when the inspection decision is made), by checking the conditions for an inspection stage change and, if necessary, storing a new inspection stage for the next inspection.

The information in the quality level determines which inspection stage will be used for the sample determination of the next inspection document. The system updates the fields in the quality level differently during dynamic modification, depending on whether dynamic modification occurs at inspection document creation or when the inspection decision is made. You define which of these times will apply in the dynamic modification rule.

Structure The quality level contains data, including the following: •

The number of inspections that have occurred since the last stage change.

•

The number of inspections that have been not OK since the last stage change.

These counters are updated each time the quality level is updated. The system uses these counters to determine when an inspection stage change should occur. You define the conditions for a stage change in the dynamic modification rule.

SAP Extended Warehouse Management (SAP EWM)

510

862

SAP Online Help

20.07.2007

Dynamic Modification You can determine the inspection frequency for a process in the Quality Inspection Engine (QIE) in different ways. For example, you can use the data from past inspection valuations to calculate the current inspection scope. To be able to react flexibly to this data, you can dynamically modify the inspection scope. This can be achieved using sampling procedures and dynamic modification rules. With respect to sample sizes and inspection probability, dynamic modification allows you to control the inspection scope for a series of inspection documents so that you will be able to achieve a predefined quality goal with a high degree of certainty. In the QIE you can perform dynamic modification at inspection document level.

Features You can use the following functions in the QIE: Description

Use

Dynamic Modification Rule

The dynamic modification rule contains the definition of the inspection stages, the dynamic modification time, and the conditions for the inspection stage changes. An inspection stage specifies inspection parameters such as the inspection severity, as well as the probability that an inspection is to be performed.

Dynamic Modification Criteria

The dynamic modification criteria are key fields that the system uses to update the quality level. The information in the quality level determines which inspection stage will be used for the sample determination of the next inspection document.

Quality Level A quality level belongs to one inspection object type and one fixed combination of properties. •

The quality level represents the current status of the dynamic modification process.

•

The quality level is always managed based on the dynamic modification criteria that are specified in the inspection rule. You can define the dynamic modification criteria used to manage the quality level with regard to the properties defined in Customizing for the corresponding inspection object type, for example, the material and vendor for goods receipt inspections, or the customer for goods issue inspections.

•

For the calculation of the inspection scope, the QIE determines the current inspection stage based on the quality level and then determines the inspection specifications accordingly.

•

At a fixed point in time, the QIE determines the inspection stage for the next inspection document based on the specified dynamic modification criteria and updates the quality level accordingly.

•

You can fix the quality level in the following ways: o

The quality level can be updated in an inspection document on the basis of the dynamic modification valuation after the inspection decision has been made (dynamic modification at inspection decision).

SAP Extended Warehouse Management (SAP EWM)

510

863

SAP Online Help o

20.07.2007

You can update the quality level when the inspection document is created (dynamic modification at inspection document creation). In this case, acceptance decisions for the outstanding document are assumed.

Note Dynamic modification at inspection document creation is useful if several new inspection documents might be created before you have completed the inspection of the first inspection document. End of the note. •

The conditions for a stage change are defined for each inspection stage in the dynamic modification rule. With the inspection stages, you can vary the probability that an inspection is to be performed between Always Inspect (100 %) and a Skip (probability of inspection 0 %) using the inspection probability. The inspection severity can change between a normal, reduced, and tightened inspection. For an inspection according to a sampling scheme, the inspection severity is used to define the sampling table which contains the valid sampling plan. Note A skip means that a certain number of inspection documents are not inspected. End of the note.

•

The dynamic modification valuation controls the stage change in the quality level for the corresponding dynamic modification criteria.

•

A stage change can cause a reduction or increase (tightening) in the inspection scope.

•

If an inspection decision is reset, the QIE tries to recalculate the quality level. If this is not possible, because new inspection documents have been created after the current inspection document, the system generates a corresponding message for the quality level and for the affected inspection documents.

Example You have the following options for dynamic modification in the QIE: How do you want to inspect?

Dynamic modification rule

Result

Two Inspection Stages: Initial stage: 1x inspection, Inspect at then switch to skip stage. predefined time intervals Skip stage: Inspection probability 0 %, maximum duration of 10 days.

Inspect a certain One inspection stage with percentage of all an inspection probability of requests 30%.

Inspect every

Two Inspection Stages:

An inspection takes place every 10 days.

30 % of all requests are inspected, 70 % are not inspected. A random generator determines which requests are inspected. Every tenth request is inspected.

SAP Extended Warehouse Management (SAP EWM)

510

864

SAP Online Help

How do you want to inspect? xth request

20.07.2007

Dynamic modification rule

Result

Initial stage: 1x inspection, then switch to skip stage. Skip stage: Inspection probability 0 %, number of acceptances = 9, then switch back to initial stage. Three inspection stages: Stage 1 (initial): Inspection severity = tightened Inspection probability = 100 %. Number of acceptances = 3. New inspection stage for reduction = stage 2. Stage 2: Inspection severity = normal.

Inspect with sampling schemes

Inspection probability = 100 3 tightened inspections are performed, followed by 2 normal inspections. Then 10 %. inspections are skipped. If there are any Number of acceptances = 2. rejections, the system switches from a normal inspection to a tightened inspection. New inspection stage for reduction = stage 3. Number of rejections = 1. New inspection stage for tightening = stage 1. Stage 3: Inspection severity = initial. Inspection probability = 0 %. Number of acceptances = 10. New inspection stage for reduction = stage 2.

You can combine the different possibilities for dynamic modification listed above.

SAP Extended Warehouse Management (SAP EWM)

510

865

SAP Online Help

20.07.2007

Quality Inspection Use You can use this function to determine whether the objects being checked constantly satisfy the quality requirements you have put in place. A quality inspection allows you to use a defect catalog to appraise the quality of an object, such as a delivery, handling unit, or product.

Integration The system processes the quality inspection in EWM using the functions in the Quality Inspection Engine (QIE). It can then forward the data to an external system such as SAP ERP, which provides enhanced functions for the quality inspection, such as inspection plans and characteristics.

Prerequisites To be able to perform a quality inspection, you must have already made the Customizing settings [Seite 853] and created the necessary master data [Seite 855].

Features The quality inspection consists of the following functions: Creation of Inspection Document [Seite 869] Inspection Object Types [Seite 871] Findings [Seite 873] Inspection Decision [Seite 874] Logistical Follow-Up Actions [Seite 876] Warehouse Management Monitor [Seite 878] The warehouse management monitor gives you an overview of the status of the quality inspections. You can see which objects are awaiting inspection and which ones have already been inspected.

SAP Extended Warehouse Management (SAP EWM)

510

866

SAP Online Help

20.07.2007

Inspection Process Purpose The main inspection processes in Extended Warehouse Management (EWM) are the inspection in goods receipt for the delivery and the warehouse-internal inspection for products. For the inspection process in goods receipt, you decide whether you want to work with or without a HU inspection, and whether the product inspection is to include samples or not. For more information about the inspection process, see QIE [Seite 888].

Process The following process is an example of an inspection process for goods receipt for the delivery. It may well be that you do not have to execute every step in your company, for example, if the products are not packed or you do not use storage control. ...

1. In EWM, there is a packed inbound delivery waiting to be processed. ○

If inspection object type Preliminary Inspection Inbound Delivery is active, the system automatically generates an inspection document for the delivery header and releases it for the inspection.

○

Active counting: The system checks whether an inspection rule exists, and also whether a corresponding dynamic modification rule exists, if required. It determines whether counting [Seite 295] is to take place, creates an inspectiondocument if required, and releases it for counting.

2. You have the option of performing the check with or without the HU inspection. a. You can only perform the HU inspection using the RF transaction [Seite 886]. b. If you do not use the HU inspection, the system calls inspection document generation for the complete quantity of delivery items at the time defined in Customizing. 3. The system changes the delivery item in terms of its stock type, according to the determined inspection rule, and writes a document flow into the delivery item. 4. If corresponding details are included in the inspection rule, the system creates samples based on the data belonging to the sample-drawing procedure. 5. If you have defined print settings [Seite 853] in Customizing for QIE accordingly, then the system automatically prints the related documents, such as: ○

Documents and sample-drawing instruction for the inspection document

○

Documents and labels for the samples

If required, you can edit the inspection document created automatically by assigning additional documents to the inspection document, or by generating additional samples for product inspections. 6. Post the goods receipt of the delivery to release the inspection document.

Once you have released an object in the QIE, you can no longer delete it. You can only cancel it or archive it. 7. If you have defined for the warehouse number that the inspection is to be forwarded to an external system, the system delegates the inspection to the external system and sends the required data from the inspection document for inspection document release. The system documents this using a status in the inspection document.

SAP Extended Warehouse Management (SAP EWM)

510

867

SAP Online Help

20.07.2007

8. You perform the inspection. If required, you use the printed documents, sampledrawing instruction, and labels. 9. You record the results of the quality inspection in the data record for the sample as follows: a. You record deviations and defects as findings. b. If required, you specify documents. c. You make an inspection decision for the sample, meaning you specify a decision code and the status Decided. You only have to set the status separately in the inspection document; in the work center, the system automatically decides on a sample when you save a decision code. The system determines a follow-up action from the inspection decision. However, you can also define this manually. d. If the inspection decisions of all samples in an inspection document are the same, the system can automatically decide on the same result for the inspection document. 10. If the system cannot decide on the inspection document automatically, or if you choose for it not to, you record defects as findings and specify documents if required. You record data for the inspection document in the same way as for the data for the sample.

If you have forwarded the inspection document to the ERP system, you can use the more extensive features of this system for recording results. For more information, see the QM documentation for the ERP system under SAP ERP Central Component → Logistics → Quality Management (QM).

Result You have performed a quality inspection. If you have performed the inspection using a sampling scheme and have defined it as such in the dynamic modification rule, the system saves the inspection decision that has been made in the quality level. The inspection decision therefore also influences the specifications for further inspections. For more information, see Dynamic Modification [Seite 907]. After you have defined the decision code, the system triggers the follow-up action that you have defined in Customizing for EWM, under Cross-Process Settings → Quality Management → Result → Define Decision Codes. There you define the key of the follow-up action being executed for the decision code. In the case of a product inspection, depending on the selected follow-up action, the system makes a transfer posting to a different stock type and generates a warehouse task for the transport of the stock that has been checked. In addition, you can create a stock transfer order in the ERP system, for example, to send the checked stock to other warehouses.

SAP Extended Warehouse Management (SAP EWM)

510

868

SAP Online Help

20.07.2007

Creation of Inspection Document Use You can use this function to create inspection documents [Extern]. In quality management (QM), you always use inspection documents to process checks. If you want to check a certain quantity of a product, you must create an inspection document in the system. You can create inspection documents automatically or manually, and use them for various types of inspection processing. As soon as you have created an inspection document, you are able to check the objects, record check results or defects, and complete the check with results recording.

The system documents the processing status of an inspection document using the inspection document status.

You can also check returns. ●

In an external system, such as SAP Customer Relationship Management (SAP CRM), you define parameters that influence goods issue and quality inspection of returns in the warehouse. Following the quality inspection, EWM sends the inspection results to SAP CRM. SAP CRM evaluates the inspection results.

●

You can use SAP CRM, for example, to control whether the returns are to be checked at all. If you do not require returns to be checked, you can immediately initiate a logistical follow-up action, such as putaway or scrapping.

For more information about inspection documents in EWM, see the EWM documentation under Connection of Delivery Processing to Quality Management [Seite 293].

Integration Depending on the requirements you have in place for generating inspection documents, you must also use delivery processing, warehouse order creation, and storage control. For checks using an external system, you also need to have integrated this external system.

Prerequisites You have executed Customizing for QM [Seite 853]. You have created the master data [Seite 855]. You have created scheduling steps [Seite 857]. You may have defined QM-specific master data [Seite 856]. You may have defined sample-drawing procedures [Seite 917].

Features The system uses the given data and properties of the inspection object type to determine additional data, such as: ●

Sample size

SAP Extended Warehouse Management (SAP EWM)

510

869

SAP Online Help ●

Inspection settings

●

Documents from the inspection rule

●

Stock type for goods receipt

●

Stock relevance of any existing samples

20.07.2007

Here, the system determines inspection settings and documents from the inspection rules that you have defined for the property values. If you have defined values for multiple properties, the system can also use multiple inspection rules.

For example, if you have defined an owner and a product, the system first uses the inspection rule that contains the owner and product. If it is unable to determine all the required arguments, it also uses the inspection rules that contain the owner only or product only. This means that the hierarchy of properties determines the sequence in which the system looks for inspection rules. For more information about this, see Inspection Specification Inheritance [Seite 923].

SAP Extended Warehouse Management (SAP EWM)

510

870

SAP Online Help

20.07.2007

Inspection Object Types Definition Inspection object types define the software component, process, and object in which you can create inspection documents [Seite 922] in the Quality Inspection Engine (QIE). ...

1. In the case of an active inspection object type, the system looks for an inspection rule. 2. If the system finds an inspection rule, it creates an inspection document dependent on the inspection object type.

Use Inspection Object Type Preliminary Inspection Inbound Delivery ●

If you activate an inbound delivery notification, the system automatically generates an inspection document for checking complete deliveries. The system requires an inspection rule for the current version of the inspection object type and warehouse number.

●

The system automatically releases the inspection document when creating it, so that it is already available when the goods physically arrive.

●

The system stores the inspection document as a reference document for the delivery header in the delivery. This document cannot contain samples or items.

Inspection Object Type Preliminary Inspection Handling Unit ●

You cannot schedule inspection documents for HUs in advance. You can only create them manually for the HU inspection using RF transaction /SCWM/RFUI.

●

For each delivery of a complete commercial truck (with multiple deliveries), you can classify all HUs as “good” or “incorrect”. When you have classified all the HUs, the system automatically creates the HU inspection document. In doing this, it generates one inspection document for each delivery and one item for each HU in this inspection document. You can also decide this directly for the “good” HUs. You then manually process the “bad” HUs in an additional process in the inspection document.

For the HU preliminary inspection, you cannot perform product inspections if you have selected Activation of Delivery or status In Yard. ●

Since you always create this inspection document manually, it makes sense to create only one inspection rule for the warehouse number and version of the inspection object.

Inspection Object Type Counting Inbound Delivery ●

The system creates this inspection document automatically, depending on Customizing for the inspection document creation within inbound delivery processing. The system releases it when it creates it. Counting is always a 100% inspection, since counting samples is irrational.

●

For counting and product inspections, the system checks the date/time of inspection document creation. If the date/time has been reached, Extended Warehouse Management (EWM) looks for an inspection rule and for any dynamic modification criteria that you may have defined.

●

Depending on the inspection rule it finds, the system changes the stock type and delivery item.

SAP Extended Warehouse Management (SAP EWM)

510

871

SAP Online Help

20.07.2007

Inspection Object Type Q-Inspection Returns Delivery ●

Providing you have not already defined the usage of returns in SAP Customer Relationship Management (SAP CRM), the system call the inspection at the defined point in time, determines an inspection rule, and checks the dynamic modification rules. For more information, see Customizing for EWM under Extended Warehouse Management → Cross-Process Settings → Quality Management → Settings for Inspection Rules.

●

If relevant, the system generates an inspection document for the inspection rule. The inspection quantity is determined from the delivery quantity.

●

Inspection documents for HUs represent a special case. You generate the inspection document for these during the HU inspection, and only use the quantity of the HUs valuated as “good“.

●

If the inspection rule contains a sample-drawing instruction, the system generates corresponding samples for the inspection document.

●

The system releases the inspection document with the first goods receipt posting, and forwards it to an external system if required. The quality inspection can then start.

Inspection Object Type Q-Inspection Product/Batch Inbound Delivery You cannot specify a usage for “standard” inbound deliveries. Inspection document creation works in the same way as for returns inbound delivery, if the preceding system has not defined a usage.

Inspection Object Type Q-Inspection Product/Batch Warehouse-Internal ●

You must create warehouse-internal product inspections manually.

●

You can either generate them using an RF environment or on the desktop.

●

You can create inspection documents for all products in a work center or HU, or restrict the inspection to a particular product.

SAP Extended Warehouse Management (SAP EWM)

510

872

SAP Online Help

20.07.2007

Findings Use When you process an inspection document, you can record the results of the inspection as characteristic values or findings. A defect is any property of an object or process that does not fulfill the specifications of an inspection characteristic. You record the defects using predefined defect codes that you have defined in Customizing. For more information, see the Implementation Guide for Extended Warehouse Management under Extended Warehouse Management → Cross-Process Settings → Quality Management. Whether findings are necessary depends on the object being checked and the inspection process Defect records can be a valuable source of information when selecting suppliers, for example. They enable quality improvements and process optimization, while reducing costs and increasing productivity at the same time. You mostly use findings in the following areas: ●

Delivery header inspection

●

Visual inspections for products and handling units

Prerequisites You have defined defects and efforts for a finding in Customizing, as well their groupings, and have assigned them to the corresponding inspection rule. For more information, see the Implementation Guide (IMG) for EWM under Extended Warehouse Management → Cross-Process Settings → Quality Management.

Features Quality management (QM) enables you to record defects in the form of defect records. You can use the defect records to analyze errors and determine their causes. You can also define the measures needed for correcting the cause of defect. This enables you to prevent the defects from reoccurring.

Information in a Defect Record A defect record may contain some or all of the following information: ●

Defect type

●

Number of defects

●

Effort for correcting defect

SAP Extended Warehouse Management (SAP EWM)

510

873

SAP Online Help

20.07.2007

Inspection Decision Use You use this function to make a decision to accept or reject the object being inspected. The inspection decision contains the results recording and follow-up action recording, and the inspection completion. ●

For inspection documents of the inspection object type Preliminary Inspection Inbound Delivery, the result is the acceptance or rejection of the delivery.

●

For inspection documents for HUs, you decide whether the contents of the HU are now to go through a standard goods receipt process, or whether you post them to blocked stock.

●

For product inspection documents, the result can be an acceptance, return delivery, stock transfer or scrapping.

You complete the inspection by making the usage decision.

Recording Findings In the finding, you record and process inspection results for samples, stock, or the inspection document. The recorded inspection results document the checked quality of a product and therefore form the basis for batch specifications. The recorded results data enables you to perform evaluations, and is therefore decisive for the follow-up actions. To record findings, you can use standard functions for the following: ●

Assign a defect to a stock, sampler, or inspection document

●

Record effort for correcting the defect

Inspection Completion After recording the results and completing the inspection, you must make a decision regarding the usage of the checked goods. You can choose between the following options: ●

You enter a decision code

●

You define follow-up actions, such as stock posting for inspection stock (for example, for freely usable stock, blocked stock, or scrap), for the inspection document, the sample, or stock.

When you make an inspection decision for the inspection document, the system then does the following: ●

It determines a quality score [Extern] for the inspection lot.

●

It updates the quality level [Seite 912] (inspection stages for the next inspection lot).

●

It may trigger an automatic follow-up action.

Usage Decision When you make the usage decision, you define whether you are accepting or rejecting the goods based on the inspection results. While you are making the usage decision, you can also record defects or perform stock posting.

Activities If you want to define your own results and follow-up actions, proceed as follows:

SAP Extended Warehouse Management (SAP EWM)

510

874

SAP Online Help

20.07.2007

...

1. Record the defects and efforts in a defect catalog. To do this, in Customizing for EWM choose Cross-Process Settings → Quality Management → Maintain Defect. 2. Connect the defect catalog of the consumer system [Extern] to the QIE using the classes stored in the ABAP Workbench, along with their methods. In Customizing, choose Cross-Application Components → Quality Inspection Engine → Define Catalogs.

Prerequisites To make a decision about the inspection, the following conditions must be fulfilled: ●

Inspection document is released (occurs at goods receipt, for example).

●

If you are working with samples, you have performed the sample inspection.

SAP Extended Warehouse Management (SAP EWM)

510

875

SAP Online Help

20.07.2007

Logistical Follow-Up Actions Use You can use logistical follow-up actions to trigger follow-up processes such as putaway, scrapping, stock transfer, or return delivery. Logistical follow-up actions are only available for the quality inspection of products. In the case of recording results for returns, for example, you can define that the returns are going back.

Integration Logistical follow-up actions generate warehouse documents [Extern] and warehouse tasks [Extern] (WTs).

Prerequisites You can define logistical follow-up actions in the following ways: ●

In Customizing for EWM under Cross-Process Settings → Quality Management → Result → Maintain Follow-Up Action.

●

Through your own implementations using /SCWM/EX_QFU and /SCWM/EX_QFU_SAVE. There you can also link the follow-up action to an exception code, for example, which then triggers a workflow or warehouse task (WT).

Features Putaway [Extern] This setting is specially for inspection object types product, inbound delivery, and return delivery. It initializes creation of a WT for putaway, if required, using the warehouse process type of the delivery item, if the stock is not packed into a handling unit with a storage control profile. In this case, the creation is done using storage control and is not influenced by QM. Due to the decision, the stock loses its reference to the sample or inspection document.

Stock Transfer ...

1. In the ERP system, you create a stock transfer order for the warehouse of the business partner who is defined in the follow-up action. The stock contains information about the inspection document, sample, or item, and receives the information that the stock in question has already been decided upon. This is the only way that the delivery for the stock transfer can pick the correct stock. 2. If you have defined a particular warehouse process type, the system creates a WT for it. 3. If inactive putaway warehouse tasks (putaway WTs) exist for the product, the system cancels them.

Return Delivery The stock loses its reference to the inspection document or sample. The system cancels any warehouse tasks that might exist, and creates a warehouse task if you have defined a warehouse process type.

Scrapping ...

1. The system looks for a stock type marked as Scrap and makes a transfer posting for the stock into this stock type.

SAP Extended Warehouse Management (SAP EWM)

510

876

SAP Online Help

20.07.2007

This makes the stock lose its reference to the inspection document or sample. 2. For a defined warehouse process type, the system issues a WT and cancels any open putaway WTs that exist.

Location-Independent Stock Type In addition to internal follow-up actions, and as an addition to the warehouse process type mentioned above, you can also define a location-independent stock type. If this differs from the current location-independent stock type, then the system determines the new stock type and makes a corresponding transfer posting for the stock.

SAP Extended Warehouse Management (SAP EWM)

510

877

SAP Online Help

20.07.2007

Warehouse Management Monitor Use The warehouse management monitor is a central tool for keeping warehouse managers constantly up-to-date as to the current situation in the warehouse, and to enable them to initiate appropriate responses in light of this situation. The warehouse management monitor also contains alert monitoring capabilities, which highlight to warehouse managers actual and potential problematic situations in the warehouse, and provide exception handling tools.

Prerequisites You have accessed the warehouse management monitor by: ...

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

Features

Node Hierarchy Tree

Upper View Area

Lower View Area

Node Hierarchy Tree The node hierarchy tree [Extern] contains all of the predefined nodes representing different object classes. The tree is used solely for navigation purposes. You can use the hierarchy tree to display in the upper view area object information for a specific node, based on selection criteria. The warehouse management monitor contains nodes for object classes relating to the following: ●

Documents such as warehouse requests (WRs) [Extern], warehouse orders (WOs), warehouse tasks (WTs), and physical inventory documents

SAP Extended Warehouse Management (SAP EWM)

510

878

SAP Online Help

20.07.2007

●

Processes such as stock and bin, and resource management [Seite 750]

●

Alerts such as overdue waves [Seite 769] or overdue deliveries without goods issue/goods receipt

Drilldown Capabilities After displaying in the upper view area object information for a node, you can drill down and display the object information for its lower-level nodes, via designated pushbuttons. You can similarly drill down to the lower-level nodes from the lower view area. List and Form Views By default, object information is displayed as a list view [Extern]. The list view is displayed in an ALV grid, and offers all standard ALV functionalities, including sorting, filtering and printing. You also have the option of toggling to form view [Extern] for a selected object. The form view provides a focused view of the object, and provides more detailed information than the list view. The form view is displayed in an HTML viewer. Methods After object information is displayed in either view area, you can call methods to perform actions on selected objects. For more information about the available methods, see Monitor Methods [Seite 882]. Customizing Options You can use the standard SAP monitor or you can create your own monitor in Customizing.

For more information about creating your own monitor, see the Implementation Guide (IMG) for EWM under Extended Warehouse Management → Monitoring → Warehouse Management Monitor. If you use the standard SAP monitor, you can tailor it to your needs by either creating variants for the standard nodes, or creating new variant nodes, based on the standard nodes. ●

Creating variants for the standard nodes enables you to use predefined selection criteria while running a session of the monitor. The variant-node assignments are lost when you close the monitor session.

●

Creating variant nodes enables you to create your own nodes, which are based on the standard nodes, but with specific selection criteria, or with a specific layout. Variant nodes are always available when the user utilizes the monitor.

SAP Extended Warehouse Management (SAP EWM)

510

879

SAP Online Help

20.07.2007

Monitor Basic Operations Use Functions Function

What You Should Know

Hide a selected node in the hierarchy tree

This operation is invoked by choosing the Hide Node option in the node’s context menu.

Show hidden nodes

This operation is invoked by choosing Show Hidden Nodes. After choosing this option, previously hidden nodes are displayed in the icon. hierarchy tree, with the

Unhide a selected node in the hierarchy tree

This operation is invoked by choosing the Unhide Node option in the node’s context menu. After choosing this option, the node icon changes to (regular node) or (variant node).

Create a variant node in the hierarchy tree

There are two options from the node’s context menu: Create Variant Node for Current Level – creates a variant node directly underneath the original node Create Variant Node for Category Level – creates a variant node under the original node, on the same level as the node’s category When creating the variant node, you have one of the following execution options: Execute – creates only the variant node based on the source node Execute with Sub-Tree – creates the variant node, as well as all of the same lower-level nodes as are contained in the source node After creating the variant node, you can create a variant for selection criteria, as well as assign to it a layout variant.

Delete variant node

This operation is invoked by choosing the Remove Node option in the node’s context menu.

Change variant node text

This operation is invoked by choosing the Rename Node option in the node’s context menu.

Display in list view object information for a node

This operation is invoked either by double-clicking the node, or choosing the Set Selection Criteria option in the node’s context menu.

SAP Extended Warehouse Management (SAP EWM)

510

880

SAP Online Help

20.07.2007

Expand all nodes in the hierarchy tree

This operation is invoked by choosing in the top tool bar.

Collapse all nodes in the hierarchy tree

This operation is invoked by choosing in the top tool bar.

Display object information of a lower-level node in the higherlevel node’s list view

This operation is invoked by selecting a row in the ALV, and choosing the pushbutton corresponding to the lower-level node. Information on the lower-level objects appears in the bottom list view.

Toggle between list and form views

You call this operation by selecting one or more rows in the ALV, and choosing from the list view tool bar. You can toggle back from form view again. to list view, by choosing

Show display transaction for object

SAP Extended Warehouse Management (SAP EWM)

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

510

881

SAP Online Help

20.07.2007

Monitor Methods Use The warehouse management monitor methods enable you to manage and control warehouse objects and processes. The methods are assigned to object classes, and carried out on specific objects within the object classes. They are implemented by utilizing function modules from content providers responsible for the object classes.

Prerequisites You have defined object class methods, and their presentation, in Customizing for Extended Warehouse Management → Monitoring → Warehouse Management Monitor → Define Object Class Methods.

Methods are included in the standard delivery. The methods are displayed as standard with the accumulated methods menu buttons.

Activities Standard Monitor Methods Method Name

Object Class Name

Display Bin

Displays data for the selected storage bin (transaction /SCWM/LS03) BIN

Storage Bin

Change Bin Print

Description

Presentation Text

Enables you to change data of the selected storage bin (transaction /SCWM/LS02) HU

Handling Unit

WO

Warehouse Order

HU

Handling Unit

WT

Warehouse Task

WO

Warehouse Order

Display HU

HU

Handling Unit

Enables you to display detailed information for an HU at a work center

Display PI Doc.

PIDIFF

Differences-{}-

Enables you to display or process a physical inventory document (transaction /SCWM/PI_PROCESS)

Process PI Doc.

PIDLOC

Storage Bin

PIDSTK

Product

PIHHU

Handling Unit

PIHIST

Doc. History

PIHLOC

Storage Bin

PIHREF

References

Reprint

Enables you to print HU or WO details

Enables you to reprint HU, WT or WO details

SAP Extended Warehouse Management (SAP EWM)

510

882

SAP Online Help

20.07.2007

PIHSTK

Product

PISLOC

Storage Bin

Maint. Resource

Enables you to maintain a selected resource [Seite 752] (transaction /SCWM/RSRC)

Logon Resource

Enables you to log on a selected resource to the desktop environment

RSRC

Resource

Logoff Resource

Enables you to log off a selected resource from the desktop environment

Send Message

Enables you to create and send a message to one or more selected resources

Assign Queue Unassign Queue

RSRCG R

Resource Group

Simulate WO

Enables you to assign/unassign a queue [Seite 764] to/from the selected resource group [Seite 754] (transaction /SCWM/QSEQ)

Enables you to simulate WO creation for one or more selected WTs, based on a specified WO creation rule. If none is specified, the system will attempt to determine one pursuant to the search sequence for WO creation rules per activity area.

Display WT Log

Displays the application log for a selected WT

Split from WO

Enables you to unassign one or more WTs from a WO, and group them into a newly-created WO.

WT

Warehouse Task

Using this method, you can determine the warehouse creation rule. If none is specified, the system will attempt to determine one pursuant to the search sequence for WO creation rules per activity area. You can also specify a reason for the split, which is stored in the exception log for WOs.

Assign WT

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

Unassign WT

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

To execute the WTs, you will need to assign them to a WO. Cancel WT

Enables you to cancel a WT

Confirm Foregr.

Enables you to confirm in the foreground one or more selected WTs or WOs (transaction /SCWM/TO_CONF)

Confirm Backgr. Create User

WT

Warehouse Task

WO

Warehouse Order

USER

User(s)

Confirms in the background one or more selected WTs or WOs Enables you to create/maintain a user (transaction /SCWM/USER)

Maintain User

SAP Extended Warehouse Management (SAP EWM)

510

883

SAP Online Help

20.07.2007

Hold Wave

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

Unhold Wave

Sets the status of the selected waves to Initial

You can perform this method only on waves of status On Hold. Delete Wave

Deletes the selected waves. WAVE

Wave

All the wave items are unassigned from the waves

Merge Wave

Merges the selected waves into one wave.

Change Wave

Enables you to change the attributes of a selected wave

Release Wave

Releases one or more selected waves

The merged wave inherits its attributes from the first wave

You can release only those waves of status Initial. Subsyste m

Activates the WOs and WTs sent to a subsystem

Split WAVITM

Wave Item

Unassign

Unassigns the selected wave items from the wave

Assign to Wave

WAVITM

Wave Item

WHRITO

Warehouse Request Item

Display WR

WHRI

Warehouse Request (Inbound)

WHRO

Displ. Insp.Doc

Enables you to assign one or more selected wave items or WR items to a specified wave

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

Warehouse Request (Outbound)

WHRI

Warehouse Request (Inbound)

WHRO

Warehouse Request (Outbound)

WHRITI

Display WO Log

Splits the selected wave items from their waves, and creates a new wave for them

Displays the inspection document(s) and inspection outcomes for a selected WR or WR item

Warehouse Request Item (Inbound)

WHRITO

Warehouse Request Item (Outbound)

WO

Warehouse Order

Displays the application log for a selected WO

SAP Extended Warehouse Management (SAP EWM)

510

884

SAP Online Help

Merge WOs

20.07.2007

Enables you to merge selected open WOs, which unassigns the WTs from the WOs, and groups them into a newly-created WO. Using this method, you can determine the warehouse creation rule. If none is specified, the system will attempt to determine one pursuant to the search sequence for WO creation rules per activity area. You can also specify a reason for the merge, which is stored in the exception log for WOs.

Hold WO

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

Open WO

Sets the status of one or more selected WOs to Open.

Add WO

Adds an empty WO to a super WO (loading/unloading scenario)

Assign Rsrce

Enables you to assign/unassign a resource to/from one or more selected WOs

Unassign Rsrce Queue ändern

Enables you to change the queue to which the selected WOs are assigned

Change LSD

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

SAP Extended Warehouse Management (SAP EWM)

510

885

SAP Online Help

20.07.2007

Quality Inspection Using Radio Frequency (RF) Use This function enables you to execute the preliminary check for inbound deliveries, and to inspect HUs or storage bins in the warehouse in an RF environment. If you do not make an inspection decision in the preliminary check for the inbound delivery, the system automatically interprets the quality inspection as using the checked object.

HU Inspection Using RF ...

1. Use the RF transaction. On the SAP Easy Access screen, choose Warehouse-Internal Processes → QM → Inspection for HU and specify the inbound delivery. 2. Specify all the “bad” then all the “good” HUs one after another. 3. The system detects when you have entered all HUs and automatically generates an inspection document for the HU inspection with one item for every HU. The system decides on the items of the “good” HUs automatically, using the default decision code. If all the HUs in a delivery are “good”, the system closes the inspection document. 4. For the contents of the “good” HUs, the system triggers inspection document creation, posts goods receipt for the complete delivery and, if “bad” HUs were included, posts the contents of the “bad” HUs into the blocked stock.

You can only execute the preliminary check for HUs in an RF environment.

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

Activities After logging on, choose Internal Processes → Quality Management. You can carry out the following checks:

Inspecting the Delivery ...

1. Choose one of the following objects to be inspected: ○

Transportation unit (TU)

○

Vehicle

○

Delivery

○

Handling unit (HU)

2. Scan the object being checked. 3. Confirm your entries.

Inspecting HUs with Goods Receipt Posting 1. Choose one of the following objects to be inspected: ○

Advanced shipping notification (ASN)

○

Delivery

○

HU

SAP Extended Warehouse Management (SAP EWM)

510

886

SAP Online Help ○

TU

○

Vehicle

20.07.2007

2. Scan the selected object. 3. Confirm your entries.

Inspecting Products 1. Choose either an HU or a storage bin for the inspection. 2. Scan the selected object. 3. Confirm your entries.

QA Counting 1. Log on to the counting station. 2. Enter the counted quantity. 3. Close counting.

SAP Extended Warehouse Management (SAP EWM)

510

887

SAP Online Help

20.07.2007

Quality Inspection Engine With the Quality Inspection Engine (QIE), you can integrate quality inspections in various SAP solutions in the mySAP Business Suite, as well as in non-sap applications. The QIE supplements the comprehensive existing quality management solution supplied by mySAP Product Lifecycle Management (mySAP PLM) and was designed for use in a heterogeneous system landscape. The QIE is service-oriented and thereby supports new processes, such as the execution of inspections using decentralized Warehouse Management in mySAP Supply Chain Management (mySAP SCM).

Implementation Considerations If your enterprise does not use mySAP PLM or mySAP Enterprise Resource Planning (mySAP ERP), which both provide comprehensive quality management functions, you can use the QIE as a lean solution to support quality inspections. If you already use quality management in mySAP PLM or mySAP ERP, you can still use the QIE for inspections in heterogeneous system landscapes (for example, if you are using decentralized Warehouse Management in mySAP SCM), or for performing inspections in new application areas. In comparison to quality management in mySAP PLM, the QIE offers additional functions providing greater flexibility when performing dynamic modification and when configuring inspection rules. Consumer systems use the QIE to perform inspection processes. End users are not even aware that the QIE is being used. As the QIE is not part of the application component, it has no knowledge of the business logic of the application component. QIE component hierarchy

Consumer system, for example mySAP SCM Request

QIE

Request

SAP Web Application Server

SAP Extended Warehouse Management (SAP EWM)

510

888

SAP Online Help

20.07.2007

Features Consumer systems can use the following functions: •

Customizing (sampling schemes, dynamic modification, document types, decision codes, samples, findings, print control, and optimization of search queries)

•

Processing of master data (inspection rule, sample-drawing instruction, and quality level)

•

Creation of inspection documents and samples (manual or automatic for goods movements)

•

Processing of inspection documents (document search, documentation of inspections with specifications, findings, and inspection decision), samples, and items

•

Archiving of inspection documents with all dependent data

•

Change document description, that is, displaying changes

•

Printing of inspection documents

Constraints The QIE does not have a dedicated user interface. All interfaces are called up by the consumer system.

SAP Extended Warehouse Management (SAP EWM)

510

889

SAP Online Help

20.07.2007

Quality Inspections with the QIE The Quality Inspection Engine (QIE) is called by a consumer system, for example, the Extended Warehouse Management System (EWM), and carries out the inspection process that was triggered in this consumer system, for example, an inspection for a goods receipt for a delivery. The consumer system system uses the QIE services. This process describes an example inspection process. For more information about the inspection process, see the documentation of the consumer system.

Process The following is an example of an inspection process for a goods receipt for a delivery. You may not have to perform all of these steps in your company, for example, if you do not use samples. 1. You define the required inspection object types in the consumer system and assign properties to these. These properties characterize the inspection object type. Examples of properties are plant, material, and vendor. In some cases, you can restrict the properties of an inspection object type to specific properties within the QIE. Whether you can do this or not depends on how an inspection object type was defined in the consumer system. For more information about defining inspection object types, see the documentation for the consumer system. 2. You define inspection rules for the different property values of the inspection object type. For example, you define inspection rules for a specific plant, or for a combination of a plant and a material. For every inspection rule, you specify arguments, that is, parameters for the inspections that are to be executed: o

By assigning an inspection procedure, you define whether or not an inspection is to be executed, and if so, whether this is to be a 100% inspection or a sampling inspection.

o

Depending on the inspection procedure used, you may also have to enter, for example, a sampling procedure and a dynamic modification rule.

o

If necessary, you assign documents. The assigned documents are passed on to the inspection document when the system creates an inspection document based on the inspection rule (see step 3).

o

You specify a code group for the valuation of inspection documents. If you want to be in a position to individually valuate samples and items in the inspection documents, you must also specify code groups for samples and items.

o

To print the documents for the inspection document and the sample-drawing instruction, you must specify an action profile of the Post Processing Framework.

o

If you want the system to automatically create samples for an inspection document when the inspection document is created, you must specify a sample type, sample-drawing procedure, and sample-drawing unit. You must only enter the sample-drawing unit for sample-drawing procedures of the type

SAP Extended Warehouse Management (SAP EWM)

510

890

SAP Online Help

20.07.2007

time or quantity. For the type container, the system dynamically determines the unit when you create or simulate an inspection. The system then uses the data of the sample type, the sample-drawing procedure, and the sample-drawing unit to create the samples. o

If you want to transfer the quality inspection data to an external system at some point during the inspection, you must specify the external system. In the external system, you can use additional functions for inspection planning and execution, for example, planning characteristics and recording results for them.

o

If you want to record defects and deviations, you must specify a finding type and a catalog filter for findings.

3. The QIE creates an inspection document. This is triggered by a process in the consumer system. If the consumer system has a suitable interface, you can also manually create an inspection document. Do do this, proceed as follows: 1. Select an inspection object type. 2. Enter values for the properties of the inspection object type. 3. You enter the lot size and the number of containers. 4. From the data you have specified, the system determines additional data, for example: ƒ

The sample size

ƒ

The inspection setup

ƒ

The documents from the inspection rule

The system determines the inspection setup and documents based on the inspection rules that you have defined for the property values. If you have specified values for more than one property, the system can use more than one inspection rule. If, for example, you have specified a plant and a material, the system first uses an inspection rule that contains both the plant and the material. If the system cannot determine all of the required arguments in this way, it can also use inspection rules that only contain the plant or only contain the material. In this process, property hierarchies determine the sequence in which the the system searches for inspection rules. See Inheritance of Inspection Specifications. For examples about the determination of the sample size, see Determination of Sample Size. 5. If the corresponding specifications are present in the inspection rule, the system creates samples based on the data in the sample-drawing procedure. Caution The system always creates only one sample record based on the sampledrawing instruction and the sample-drawing unit. If the sample-drawing unit requires that several sample records be created, for example, if five samples are to be taken every two hours, the consumer system must create the additional sample records, for example, by copying the first set. End of the caution. 6. The system copies the documents from the inspection rule. If necessary, you can assign additional documents to the inspection document.

SAP Extended Warehouse Management (SAP EWM)

510

891

SAP Online Help

20.07.2007

7. You save the inspection document. 8. If you have defined the action profiles in the Customizing of the QIE, the system automatically prints the documents, for example: ƒ

Documents and sample-drawing instructions for the inspection document

ƒ

Documents and labels for samples

9. You release the inspection document. Note Once you have released an object in the QIE, it is no longer possible to delete this object. You can only cancel or archive it. End of the note. 10. If, in the inspection rule, you defined that data should be transferred to an external system, the system delegates the inspection to the external system and sends the data required from the inspection document. 4. You execute the inspection. In doing so, you can use the printed documents, sampledrawing instruction, and labels. 5. You record the results of the inspection as follows in the data record of the sample: 0. You record deviations and defects as findings. 1. If necessary, you specify documents. 2. You make the inspection decision for the sample, that is, you specify a decision code and the status decided. 6. You record the data for the inspection document in the same way as those for the sample. In doing so, you can refer to the data that you recorded for the samples. Note If you have transferred an inspection document to an external system, such as mySAP Enterprise Resource Planning (mySAP ERP), you can use the more comprehensive functions for results recording that are available in this system. For more information, see the documentation of the external system. End of the note.

Result You have carried out a quality inspection using the QIE. If you executed the inspection with a sampling scheme and if you made the corresponding settings in the dynamic modification rule, the inspection decision that has been made will be saved in the quality level. In this way, the inspection decision influences the specifications for the next inspection. For more information, see Dynamic Modification. The selected decision code determines whether or not a follow-up action must be executed in the consumer system. In Customizing for the QIE, you define the key of the follow-up action for the decision code under Define Decision Codes. The QIE transfers this key to the consumer system. The consumer system interprets the key and executes the follow-up action.

SAP Extended Warehouse Management (SAP EWM)

510

892

SAP Online Help

20.07.2007

More Information For detailed information and examples of how the consumer system interacts with the QIE, see Interaction Between the Systems.

SAP Extended Warehouse Management (SAP EWM)

510

893

SAP Online Help

20.07.2007

Determination of the Sample Size This is an example process that shows how the system determines sample sizes for different inspection procedures.

Process Based on the inspection object type and the properties, the system determines the inspection rule arguments that are valid for the inspection. These arguments can stem from several inspection rules (see Inheritance of Inspection Specifications). The inspection rule arguments determine the inspection procedure, which in turn specifies how the sample size is to be determined.

Determination of the Sample Size for a 100% Inspection If the inspection rule arguments specify that there is to be no dynamic modification and that the inspection procedure is to be a 100% inspection, the system uses the lot size as the sample size.

Inspection object type

Properties

Lot size

Inspection rule

Inspection procedure (in this case: 100% inspection)

Sample size = lot size

Legend: Input for inspection Result with which the inspection document is created

Determination of the Sample Size for a Sampling Inspection In the following example, the inspection rule arguments define the following: •

The inspection procedure sampling inspection is used.

•

The sampling type sampling scheme is used as the sampling procedure.

•

The sampling scheme is an ISO sampling scheme.

SAP Extended Warehouse Management (SAP EWM)

510

894

SAP Online Help

20.07.2007

•

Dynamic modification takes place.

•

A sample-drawing procedure is used.

Based on this, the system determines the sample size as follows: 1. Dynamic modification defines whether or not an inspection is to take place and what the inspection severity should be if the inspection takes place. If there is to be no inspection (skip), the following steps are not executed. 2. The sampling scheme defines the quantity that has to be inspected based on the specified lot size and on the inspection severity defined in the previous step, as well as the conditions for an acceptance or rejection. 3. The sample-drawing procedure and, in some cases, the sample-drawing unit define the quantity that must be inspected based on the specified lot size and on the number of containers. They also define how this quantity is distributed among individual samples. To do this, the system evaluates the sample-drawing instructions. The sample-drawing instruction can use a sampling scheme to determine the total sample quantity. In the sample-drawing procedure, a sampling scheme is only used to determine the sample quantity. The acceptance and rejection numbers from the sampling scheme are ignored. As the sample-drawing instruction contains its own inspection severity, inspection level, and acceptable quality level (AQL), the sampling scheme of the sample-drawing procedure is evaluated independently of other inspection rule arguments (AQL, inspection severity based on the quality level). 4. The system supplements the data from step 3 (total sample size) with the data from the step 2 (preliminary sample size). For example, the total sample size can specify the number of samples, but not the size of each individual sample. The sample size is taken from the data of the preliminary sample size. The system calculates the individual sample size based on the sample size. Conversely, the sample-drawing procedure can specify the size of the individual sample, but then it does not specify the number of samples. The preliminary sample size is used to determine as the number of samples. If the total sample size contains both the number of samples and the size of the individual samples, the system does not take the preliminary sample size into consideration. Inspection object type

Properties

Lot size

Number of containers

Inspection rule

Inspection procedure (In this case: sampling inspection with sample-drawing procedure of the sampling type sampling scheme) Dynamic modification criteria (Æ by which properties is dynamic modification performed) Dynamic modification rule (list of insp. stages Æ such as (quant.) In Dynamic Modification)

AQL

Sampling scheme (List of sampling plans) Inspection level (approximate regulator for sample size)

Sample-drawing procedure Sanple-drawing unit

Quality level Valid inspection stage 1 Likelihood of inspection

Inspection severity (detailed regulator for sample size)

If skipped: STOP here Sample range 2

Acceptance/rejection number

Preliminary sample size 3

Sample-drawing instruction Legend: Input for inspection

4

Result with which the inspection document is created

Total sample size

Sample size

SAP Extended Warehouse Management (SAP EWM)

510

895

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

896

SAP Online Help

20.07.2007

System Interaction This process describes how a consumer system interacts with the Quality Inspection Engine (QIE).

Prerequisites The consumer system provides the user interface.

Process 1. You call up the application that you require in the consumer system. 2. The consumer system checks if you have authorization to use this application. 3. In the consumer system, you select the function you require within the application and enter data. 4. The consumer system transfers the data to the QIE and calls up the associated service in the QIE. 5. The QIE checks if you have authorization to use this service. 6. Depending on the service, the QIE executes one or more of the following steps: o

It reads or loads data.

o

It checks data.

o

It changes data.

o

It deletes data.

o

It saves data.

7. The QIE makes the processed data available to the consumer system. 8. The consumer system picks up, interprets, and processes the data and makes it available to you if required. System Interaction

SAP Extended Warehouse Management (SAP EWM)

510

897

SAP Online Help

Consumer system

20.07.2007

QIE

Call of the application Authorization check Call of the function, data entry Data transfer, call of the service

Authorization check Data processing

Interpretation and processing of the data

Retrieval of the data

This process flow can be repeated as often as required during a process. See the following example.

Example The following process flow is an example of how the systems interact when you display the findings for an inspection document: 1. In the consumer system, you choose the transaction for the administration of findings. 2. The consumer system checks if you have authorization to use this transaction. 3. In the consumer system, you select the function for displaying findings and enter the inspection document for which you want the findings to be displayed. 4. The consumer system transfers the number of the inspection document to the QIE and calls the service for displaying findings there. 5. The QIE checks if you have authorization to use this service. 6. Based on the transferred inspection document number, the QIE reads data for the inspection document and the associated findings. 7. The QIE makes a list of findings available to the consumer system. 8. The consumer system picks up the list of findings and displays it on the user interface. If you then decide than a finding needs to be processed, the process flow will restart at step 3 when you select the function for changing findings. The following process flow is an example of how the system creates an inspection document in the background when you create a goods receipt:

SAP Extended Warehouse Management (SAP EWM)

510

898

SAP Online Help

20.07.2007

1. In the consumer system, you choose the transaction for the creating goods receipts. 2. The consumer system checks if you have authorization to create goods receipts. 3. In the consumer system, you enter the data required for the goods receipt, for example, the material and the plant. 4. The consumer system transfers the material and the plant to the QIE and calls the service for creating inspection documents there. 5. The QIE checks if you have authorization to use the service for creating inspection documents. 6. Based on the transferred material and plant data, the QIE evaluates the corresponding inspection rules, determines the inspection parameters, creates the inspection document based on these parameters, and if necessary created the associated samples. If necessary, the system can execute other follow-up actions. For example, it can print sample-drawing instructions. 7. The QIE informs the consumer system that an inspection must take be carried out, that an inspection document has been created, and it tells it the number of this inspection document. 8. The consumer system picks up the information that an inspection must be carried out. If you have made the corresponding settings, the consumer system will flag the goods receipt document accordingly.

SAP Extended Warehouse Management (SAP EWM)

510

899

SAP Online Help

20.07.2007

Inspection Object Type Defines the software component, the process, and the object for which inspection documents can be created in the Quality Inspection Engine (QIE), for example, for Extended Warehouse Management (EWM) for the receipt of materials (material inspection).

An inspection object type is created in the QIE from the consumer system. The key of the inspection object type contains the process, software component, and object type to be inspected. In addition to the key fields, you also define properties when you create an inspection object type in the consumer system. These properties are relevant for determining inspection rules. Examples of properties are plant, material, and vendor. In some cases, you can restrict the properties of an inspection object type to specific properties within the QIE. Whether you can do this or not depends on how an inspection object type was defined in the consumer system. For more information about defining inspection object types, see the documentation for the consumer system. For an inspection object type, you define inspection rules for specific values of the properties or for specific values of property combinations. For example, you define an inspection rule for a material from a specific vendor. If the QIE is called from the business process in the consumer system, inspection documents can be created for the related inspection object type. Detailed inspection specifications are taken from the inspection rule. These are valid for the current property values transferred from the process.

SAP Extended Warehouse Management (SAP EWM)

510

900

SAP Online Help

20.07.2007

Inspection Rule Rule in which you specify: •

The specifications for the creation of an inspection document (inspection procedure)

•

The type of determination of the inspection scope (inspection procedure, sampling procedure)

•

The specifications for the inspection frequency (dynamic modification)

•

The code for the inspection decision

You can also attach documents, such as an inspection instruction, to the inspection rule.

You create and process the inspection rule in the consumer system of the Quality Inspection Engine (QIE). If the consumer system triggers the creation of an inspection document in the QIE, the QIE finds the valid inspection rule with its inspection specifications based on the current values of the properties for the inspection object type. Examples of properties are plant, material, and vendor. An inspection rule is valid for one inspection object type and for the specific values of the properties assigned to this inspection object type. You can create several inspection rules for the different property values for one inspection object type, for example, you can define different inspection rules for different materials, for different vendors, or for combinations of material and vendor.

Structure An inspection rule consists of the following: •

Inspection procedure

•

Sampling procedure

•

Dynamic modification rule and dynamic modification criteria

•

Valuation rule

•

Decision codes

•

Document assignment

•

Action profile of the Post Processing Framework for printing documents and sampledrawing instructions

•

Sample type, sample-drawing procedure with sample-drawing unit and sampledrawing instruction

•

Finding type and catalog filter for findings

SAP Extended Warehouse Management (SAP EWM)

510

901

SAP Online Help

20.07.2007

Inspection Procedure Procedure that defines whether an inspection is to take place or not. If an inspection is to take place, the inspection procedure defines whether this is to be a 100% inspection or a sampling inspection. You can select different sampling procedures for sampling inspections.

The inspection procedure is the basis for an inspection rule. Depending on the inspection procedure used, the consumer system of the Quality Inspection Engine (QIE) can transfer additional data for the inspection rule, for example, data related to the sampling procedure, dynamic modification, and the valuation.

SAP Extended Warehouse Management (SAP EWM)

510

902

SAP Online Help

20.07.2007

Sample Determination The automatic determination of samples is a part of the inspection process. The sampling procedures, sampling schemes, and dynamic modification rules serve as the basic data for the sample determination process. To adapt the inspection to the current quality level, the system can dynamically modify the inspection scope. Using the sampling procedures and dynamic modification rules stored in the inspection rule, the system modifies the inspection scope and the inspection frequency according to the current quality level.

Integration In accordance with your specifications, the Quality Inspection Engine (QIE) draws the information for sample determination from the following sources: Basic Data Sampling procedure

Sampling Scheme

Meaning The sampling procedure defines the rules for determination of the sample size. The sample size can be specified as a fixed value, as a percentage of the lot size, or as a sampling scheme. The sampling scheme contains information for drawing samples, based on the size of the inspection lot and various inspection severities or values of the Acceptable Quality Level (AQL). If you assigned a sampling scheme to a sampling procedure, the system calculates the sample sizes to be used to inspect the object based on the lot size and the inspection severity (or inspection severity and AQL value).

The sampling plan is part of the sampling scheme. The sampling plan Sampling Plan includes the information about the sample sizes and the criteria that are to be used to valuate the results of the sampling inspection.

Dynamic Modification Rule

The dynamic modification rule contains the definition of the inspection stages, the dynamic modification time, and the conditions for the inspection stage changes. An inspection stage specifies inspection parameters such as the inspection severity, as well as the probability that an inspection is to be performed.

More Information For examples about the determination of the sample size, see Determination of Sample Size.

SAP Extended Warehouse Management (SAP EWM)

510

903

SAP Online Help

20.07.2007

Sampling Procedure The sampling procedure contains the rules for calculating the sample size for a sample inspection.

You define the rules for sample calculation depending on the sampling type in the inspection rule. The system uses a sampling procedure in the inspection rule if you select Sampling Inspection as the inspection procedure.

Sampling Type The sampling type of a sampling procedure specifies how the sample is determined by the system. Examples are: •

Fixed sample

•

Use of a sampling scheme

•

Percentage sample

•

Individual sample determination using a BAdI implementation

Depending on the sampling type, different specifications must be made for sample determination, for example, for the sampling size for a fixed sample.

Valuation Mode The valuation mode (for example, attributive inspection of nonconforming units, attributive inspection of number of defects, manual valuation) defines rules for the acceptance and rejection of an inspection document. The sampling type and the valuation mode specify which parameters the system uses to determine a valuation proposal.

SAP Extended Warehouse Management (SAP EWM)

510

904

SAP Online Help

20.07.2007

Sampling Scheme Contains sampling plans and determines how acceptance and rejection decisions are made. A sampling plan determines the sample size for a specific inspection severity and a specific lot size. With the Quality Inspection Engine (QIE), you can use sampling schemes that are in accordance with international standards (for example, ISO 2859), as well as ones that comply with company-specific standards.

Structure The sampling scheme supplies values for the following elements depending on the lot size and the inspection severity: •

Sample size

•

Acceptance number (this depends on the value of the Acceptable Quality Level (AQL).

•

Rejection number (this depends on the AQL value)

Note If you wish to work without an AQL value, you must create a dummy AQL value. End of the note. The AQL value is the maximum fraction of nonconforming units (as a percentage) or maximum number of defects per 100 units permitted for a lot to be accepted. The AQL is the quality level that represents the upper limit of a satisfactory average quality level for an acceptance sampling inspection. In the QIE, the inspection severity serves as an identifier for a normal, reduced, or tightened inspection. By varying the inspection severity, you can flexibly adjust the probability of acceptance and the inspection effort, based on different quality situations. The inspection severity is closely connected to the inspection scope. If all other conditions remain the same, different inspection severities lead to different inspection scopes or acceptance conditions.

SAP Extended Warehouse Management (SAP EWM)

510

905

SAP Online Help

20.07.2007

Sampling Plan Instruction containing the required information about the sample size.

For every value of the acceptable quality level (AQL value), the sampling scheme contains a table of sampling plans for each inspection severity. This table is sorted according to the lot size.

Structure Lot Size The lot size gives the quantity of the population (measured in sample units) as an upper limit, up to which the relevant sampling plan applies. In every table with sampling plans that you have created within a sampling scheme, also enter the largest possible lot size. If you enter a value greater than the maximum allowed value (2,147,483,647), an error message will appear. If, in sample determination, you use a lot size that is greater than the maximum interval specified in a table of sampling plans, the system cannot determine the sample size, and a 100% inspection is performed.

Sample size The sample size is the quantity of units (calculated in sample units) taken from a population or subpopulation in order to be inspected.

Acceptance Code c You use the acceptance code c in a sampling inspection for an attributive inspection to define the highest number of nonconforming units or defects in the sample that still allow the sample to be accepted.

Rejection Code d You use the rejection code d in a sampling inspection for an attributive inspection to define the lowest number of nonconforming units or defects in the sample that lead to the rejection of the sample.

SAP Extended Warehouse Management (SAP EWM)

510

906

SAP Online Help

20.07.2007

Dynamic Modification You can determine the inspection frequency for a process in the Quality Inspection Engine (QIE) in different ways. For example, you can use the data from past inspection valuations to calculate the current inspection scope. To be able to react flexibly to this data, you can dynamically modify the inspection scope. This can be achieved using sampling procedures and dynamic modification rules. With respect to sample sizes and inspection probability, dynamic modification allows you to control the inspection scope for a series of inspection documents so that you will be able to achieve a predefined quality goal with a high degree of certainty. In the QIE you can perform dynamic modification at inspection document level.

Features You can use the following functions in the QIE: Description

Use

Dynamic Modification Rule

The dynamic modification rule contains the definition of the inspection stages, the dynamic modification time, and the conditions for the inspection stage changes. An inspection stage specifies inspection parameters such as the inspection severity, as well as the probability that an inspection is to be performed.

Dynamic Modification Criteria

The dynamic modification criteria are key fields that the system uses to update the quality level. The information in the quality level determines which inspection stage will be used for the sample determination of the next inspection document.

Quality Level A quality level belongs to one inspection object type and one fixed combination of properties. •

The quality level represents the current status of the dynamic modification process.

•

The quality level is always managed based on the dynamic modification criteria that are specified in the inspection rule. You can define the dynamic modification criteria used to manage the quality level with regard to the properties defined in Customizing for the corresponding inspection object type, for example, the material and vendor for goods receipt inspections, or the customer for goods issue inspections.

•

For the calculation of the inspection scope, the QIE determines the current inspection stage based on the quality level and then determines the inspection specifications accordingly.

•

At a fixed point in time, the QIE determines the inspection stage for the next inspection document based on the specified dynamic modification criteria and updates the quality level accordingly.

•

You can fix the quality level in the following ways: o

The quality level can be updated in an inspection document on the basis of the dynamic modification valuation after the inspection decision has been made (dynamic modification at inspection decision).

SAP Extended Warehouse Management (SAP EWM)

510

907

SAP Online Help o

20.07.2007

You can update the quality level when the inspection document is created (dynamic modification at inspection document creation). In this case, acceptance decisions for the outstanding document are assumed.

Note Dynamic modification at inspection document creation is useful if several new inspection documents might be created before you have completed the inspection of the first inspection document. End of the note. •

The conditions for a stage change are defined for each inspection stage in the dynamic modification rule. With the inspection stages, you can vary the probability that an inspection is to be performed between Always Inspect (100 %) and a Skip (probability of inspection 0 %) using the inspection probability. The inspection severity can change between a normal, reduced, and tightened inspection. For an inspection according to a sampling scheme, the inspection severity is used to define the sampling table which contains the valid sampling plan. Note A skip means that a certain number of inspection documents are not inspected. End of the note.

•

The dynamic modification valuation controls the stage change in the quality level for the corresponding dynamic modification criteria.

•

A stage change can cause a reduction or increase (tightening) in the inspection scope.

•

If an inspection decision is reset, the QIE tries to recalculate the quality level. If this is not possible, because new inspection documents have been created after the current inspection document, the system generates a corresponding message for the quality level and for the affected inspection documents.

Example You have the following options for dynamic modification in the QIE: How do you want to inspect?

Dynamic modification rule

Result

Two Inspection Stages: Initial stage: 1x inspection, Inspect at then switch to skip stage. predefined time intervals Skip stage: Inspection probability 0 %, maximum duration of 10 days.

Inspect a certain One inspection stage with percentage of all an inspection probability of requests 30%.

Inspect every

Two Inspection Stages:

An inspection takes place every 10 days.

30 % of all requests are inspected, 70 % are not inspected. A random generator determines which requests are inspected. Every tenth request is inspected.

SAP Extended Warehouse Management (SAP EWM)

510

908

SAP Online Help

How do you want to inspect? xth request

20.07.2007

Dynamic modification rule

Result

Initial stage: 1x inspection, then switch to skip stage. Skip stage: Inspection probability 0 %, number of acceptances = 9, then switch back to initial stage. Three inspection stages: Stage 1 (initial): Inspection severity = tightened Inspection probability = 100 %. Number of acceptances = 3. New inspection stage for reduction = stage 2. Stage 2: Inspection severity = normal.

Inspect with sampling schemes

Inspection probability = 100 3 tightened inspections are performed, followed by 2 normal inspections. Then 10 %. inspections are skipped. If there are any Number of acceptances = 2. rejections, the system switches from a normal inspection to a tightened inspection. New inspection stage for reduction = stage 3. Number of rejections = 1. New inspection stage for tightening = stage 1. Stage 3: Inspection severity = initial. Inspection probability = 0 %. Number of acceptances = 10. New inspection stage for reduction = stage 2.

You can combine the different possibilities for dynamic modification listed above.

SAP Extended Warehouse Management (SAP EWM)

510

909

SAP Online Help

20.07.2007

Dynamic Modification Criteria The dynamic modification criteria define the properties that are the basis for combining inspections for dynamic modification. The dynamic modification criteria are key fields that the system uses to update the quality level. On the basis of these key fields, the system dynamically changes the sample sizes.

You define the dynamic modification criteria in Customizing of the Quality Inspection Engine (QIE). You create these criteria with reference to an inspection object type by selecting one or more properties that are defined for the inspection object type for updating the quality level.

SAP Extended Warehouse Management (SAP EWM)

510

910

SAP Online Help

20.07.2007

Dynamic Modification Rule Basic data record containing the definition of the inspection stages, the dynamic modification time (at inspection document creation or after the inspection decision has been made), and the conditions for the inspection stage change. The stage changes depend on the inspection results for inspection documents, that is, they depend on whether the inspection documents are accepted or rejected. The stage changes can also be specified in the dynamic modification rule.

You can use dynamic modification rules to vary or dynamically control the inspection scope, whether an inspection is to take place or not.

Structure A dynamic modification rule contains the following: •

The definition of the inspection stages

•

The time of dynamic modification

•

The conditions that cause an inspection stage change

•

An optional reset period after which the system reverts to the initial inspection stage

The following options always apply to the conditions for an inspection stage change: •

The OK case

•

The not OK case

The conditions are used to update the quality level, which always reflects the current status of dynamic modification. In the inspection stages, you can define the inspection frequency and an inspection probability between 0% and 100%. This allows you to define inspection frequencies, for example: As long as the quality level is within an inspection stage, an inspection will be performed in 30% of cases and no inspection will be performed in 70% of cases. The system uses a random generator to determine when inspections are performed or not performed.

SAP Extended Warehouse Management (SAP EWM)

510

911

SAP Online Help

20.07.2007

Quality Level Data record that the system automatically updates at the time of dynamic modification (at inspection document creation or when the inspection decision is made), by checking the conditions for an inspection stage change and, if necessary, storing a new inspection stage for the next inspection.

The information in the quality level determines which inspection stage will be used for the sample determination of the next inspection document. The system updates the fields in the quality level differently during dynamic modification, depending on whether dynamic modification occurs at inspection document creation or when the inspection decision is made. You define which of these times will apply in the dynamic modification rule.

Structure The quality level contains data, including the following: •

The number of inspections that have occurred since the last stage change.

•

The number of inspections that have been not OK since the last stage change.

These counters are updated each time the quality level is updated. The system uses these counters to determine when an inspection stage change should occur. You define the conditions for a stage change in the dynamic modification rule.

SAP Extended Warehouse Management (SAP EWM)

510

912

SAP Online Help

20.07.2007

Dynamic Modification at Inspection Document Creation The system immediately updates the quality level for the current inspection document during sample determination if you set the time indicator Inspection Creation in the dynamic modification rule.

Integration With dynamic modification at document creation, the system automatically valuates the inspection document with an acceptance, increases the number of successful inspections (OK case) by one, and checks whether the conditions for a stage change have been met. If this is the case, a stage change is made in the quality level, which then affects the next inspection document. If the inspection document is rejected during inspection document processing, the system updates the quality level for an unsuccessful inspection (not OK case) after the inspection decision has been made. Note A subsequent change in the quality level does not affect inspection documents that were created in the meantime. End of the note.

Features Updating the Quality Level (With Immediate Dynamic Modification) When an inspection document is created, the following scenarios are possible: Quality level does not exist yet

Quality level already exists The system:

The system creates a quality level. The quality level is managed in accordance with the criteria defined in the inspection rule. The quality level is processed based on the properties defined as inspection criteria in the inspection rule.

•

Checks the reset period

•

Checks the maximum duration

•

Determines the valid inspection stage

•

Updates the inspection document number using the current document number

•

Automatically sets the field for the dynamic modification valuation to accepted

•

Increases the counter for the number of inspections since the inspection stage change by one

•

Executes a stage change if the conditions for a stage change have been fulfilled; it then updates the counters

SAP Extended Warehouse Management (SAP EWM)

510

913

SAP Online Help

Quality level does not exist yet

20.07.2007

Quality level already exists

The system uses the initial inspection stage in the dynamic modification rule as the current inspection stage in the new quality level. When the inspection decision is made and if it is a rejection, the system updates the field Dynamic Modification Valuation. Then the system carries out the following steps: •

It increases the counter for the number of inspections that were rejected since the inspection stage change by one.

•

The system initiates a stage change if the conditions for a stage change have been fulfilled.

•

The system updates the field Date of Last Inspection.

SAP Extended Warehouse Management (SAP EWM)

510

914

SAP Online Help

20.07.2007

Dynamic Modification at Inspection Decision The system updates the quality level for the current inspection document when the inspection decision is made if you set the time Inspection Decision in the dynamic modification rule.

Integration When the inspection decision is made for the current inspection document, the system updates the quality level based on the dynamic modification rule.

Features Updating the Quality Level (Dynamic Modification at Inspection Decision) When an inspection document is created, the following scenarios are possible: Quality level does not exist yet

Quality level already exists The system:

The system creates a quality level. The quality level is managed in accordance with the criteria defined in the inspection rule. The quality level is processed based on the properties defined as inspection criteria in the inspection rule.

•

Checks the reset period

•

Checks the maximum duration

•

Determines the valid inspection stage

•

Increases the counter for the number of inspections since the inspection stage change by one

•

Stores the number of the current inspection document in the Inspection Document Without Decision field

•

Increases the counter Inspections since stage change for inspection documents without an inspection decision by one

The system uses the initial inspection stage in the dynamic modification rule as the current inspection stage in the new quality level. When the inspection decision is made, the system updates the quality level: •

The system stores the number of the current inspection document in the relevant field.

•

The system stores the valuation of the inspection document (acceptance or rejection) in the field for the inspection decision for the document.

•

The system reduces the counter for the inspection documents without an inspection decision by one.

SAP Extended Warehouse Management (SAP EWM)

510

915

SAP Online Help

20.07.2007

•

The system increases the counter for the number of inspections that were rejected since the inspection stage change by one.

•

The system initiates a stage change if the conditions for a stage change have been fulfilled.

•

The system updates the field Date of Last Inspection.

SAP Extended Warehouse Management (SAP EWM)

510

916

SAP Online Help

20.07.2007

Sample-Drawing Procedure Master data record that regulates how samples are taken and formed.

Structure You enter the following data in the sample-drawing procedure: •

You define the type of sample drawing. That is, you choose one of the following options: o

The samples are taken at predefined time intervals, for example, every five hours.

o

The samples are taken at predefined quantity intervals, for example, every 500 kg.

o

The samples are taken on a per container basis, for example, one sample for each pallet.

o

The samples are taken in accordance with the specifications that you defined in Customizing for the Quality Inspection Engine in the Business Add-In (BAdI) QIE Sample Calculation.

•

You define the sample-drawing units.

•

You define the sample-drawing instructions for the sample-drawing units.

Integration The sample-drawing procedure is a collection of sample-drawing units. The sample-drawing procedure itself does not contain any data for the sample drawing. You can define any number of sample-drawing units for a sample-drawing procedure. For every sample-drawing unit you can specify sample-drawing instructions for the following sample categories: •

Primary sample

•

Pooled sample

•

Reserve sample

Note the following: •

For reserve samples, you may only specify a maximum of one sample-drawing instruction.

•

If you specify more than one sample-drawing instruction for primary samples, you may not specify any sample-drawing instructions for pooled samples.

•

If you specify one or more sample-drawing instructions for pooled samples, you must specify exactly one sample-drawing instruction for primary samples. This sampledrawing instruction defines the primary samples that are mixed together to form the pooles samples.

You can specify the following sample-drawing instructions for one sample-drawing unit: Possible Number of Sample-Drawing Instructions for Each Sample Category (n = 1, 2, 3, ...)

SAP Extended Warehouse Management (SAP EWM)

510

917

SAP Online Help

20.07.2007

Primary sample

Pooled sample

Reserve sample

n

0

0

n

0

1

1

n

0

1

n

1

0

0

1

Note the following for the sample quantity that you specify in the sample-drawing instructions: •

You must either specify the sample quantity for none or for all of the sample drawing instructions for a sample-drawing unit.

•

If you specify more than one sample-drawing instruction for pooled samples or primary samples, all of these sample-drawing instructions must contain a sample quantity and these sample quantities must have the same unit.

If you specify sample-drawing instructions that do not adhere to these specifications, the system ignores these sample-drawing instructions and creates a primary sample that includes the whole sample quantity when the sample calculation for the inspection document is executed. If, when the system creates the inspection document based on the inspection rule, the system finds a sample-drawing procedure as well as a sampling procedure, it will initially only take the sample-drawing procedure into consideration. Only if the system cannot find all the data it requires in the sample-drawing procedure, will it take the sampling procedure into consideration.

SAP Extended Warehouse Management (SAP EWM)

510

918

SAP Online Help

20.07.2007

Sample-Drawing Unit Specifies the time or quantity interval at which samples are to be taken, or the lot containers from which samples are to be taken.

Example The possible sample-drawing units depend on the type of sample-drawing procedure. For example: Type of sample-drawing procedure

Example of a sampledrawing unit

Meaning

Time

Two hours

Samples are taken every two hours.

Container

Pallet

Samples are taken from each pallet.

Quantity

500 pieces

Samples are taken every 500 pieces.

SAP Extended Warehouse Management (SAP EWM)

510

919

SAP Online Help

20.07.2007

Sample-Drawing Instruction Instruction that contains all required information for taking one or more samples from a population to be inspected.

In the sample-drawing instruction, you define how samples are to be processed during the inspection.

Structure You can define the following in the sample-drawing instruction: •

You define the type of sample-drawing instruction. That is, you choose one of the following: o

A fixed number of samples is used.

o

A sampling scheme is used.

o

An individual sample-drawing instruction is used, which you defined in Customizing for the Quality Inspection Engine in the Business Add-In (BAdI) Individual Sample-Drawing Instruction.

•

You define the target for the samples, for example, the laboratory that processes the samples.

•

You define the sample number.

•

You define the sample quantity and the unit of the sample quantity.

•

You define the sample container in which the samples are to be collected.

Depending on the type of sample-drawing instruction you have chosen, you may be able to specify additional information.

SAP Extended Warehouse Management (SAP EWM)

510

920

SAP Online Help

20.07.2007

Document Assignment You can assign documents to the following objects: •

Inspection rule

•

Inspection document

•

Sample

•

Item

By assigning documents, you can store comprehensive additional information about an inspection. Examples of documents are inspection instructions or drawings in a variety of formats. Possible formats include DOC, XLS, and JPG.

SAP Extended Warehouse Management (SAP EWM)

510

921

SAP Online Help

20.07.2007

Inspection Document Data record that collects all information and data pertaining to an inspection. An inspection document is created as soon as an inspection is triggered by a consumer system.

Structure An inspection document contains the following information about the object to be inspected: •

Inspection specifications

•

Inspection results

•

Inspection decision

Documents can be assigned to the inspection document or to the inspection rule on which it is based. A message log also exists for the inspection document.

SAP Extended Warehouse Management (SAP EWM)

510

922

SAP Online Help

20.07.2007

Inheritance of Inspection Specifications You can create as many inspection rules as required for each inspection object type. Each inspection rule is valid for a defined combination of values of properties that are relevant to the inspection object type and are flagged as relevant for inspection documents. Examples of properties are plant, material, and vendor. Examples of property values are the actual plant, material, or vendor. The properties for an inspection object type have a predefined hierarchy that determines the order in which the system searches for the valid inspection rules. This hierarchy keeps the number of steps required to find the relevant inspection rule to a minimum.

Example Hierarchy structure of selected property combinations

SP1

Mat. GR

Inspection object type

DMC1 DMR1 CdG3

Plant

0001 DMR2

Material

4711 SP2

4712

4711

SP3

4712 CdG1

SP2 CdG2

Vendor

1000 SP3

2000 SP4

DMR3

In the graphic, each hierarchy node (blue) represents the value of a property for the inspection object type or the inspection object type itself (in this case: Mat GR). The yellow rectangles contain the corresponding specifications from the inspection rule for the relevant value combination. The determination of the inspection rule is based on the following principles: •

The values of the inspection properties are evaluated individually or in groups. For example, all inspection properties for a sampling procedure are evaluated together. The sample-drawing procedure and the sample-drawing unit are also evaluated together. The inspection specifications for an inspection can originate in different inspection rules.

SAP Extended Warehouse Management (SAP EWM)

510

923

SAP Online Help •

20.07.2007

If no specific inspection rule exists for the combination of property values for the inspection object type, the system uses the specifications from the next higher-level inspection rule that it finds.

In the example above, the combination of sampling procedure 1, dynamic modification criterion 1, dynamic modification rule 1, and code group 3 is valid for the inspection decision for all inspections created for a material goods receipt (inspection object type Mat GR). However, in plant 0001, the dynamic modification rule 2 is valid. This gives rise to the following combination: Sampling procedure 1, dynamic modification criterion 1, dynamic modification rule 2, and code group 3. This combination is valid in plant 0001 for all materials except material 4711 (sampling procedure 2, dynamic modification criterion 1, dynamic modification rule 2, and code group 3) and material 4712 (sampling procedure 3, dynamic modification criterion 1, dynamic modification rule 2, and code group 3). A special code group (code group 1) for inspection decisions is valid for material 4711 in all plants and for all vendors. This results in the following inspection specification determination:

Example Plant Material Vendor

Sampling procedure

Dynamic modification criterion (DMC)

Dynamic modification rule (DMR)

Code group (CdG)

1

0002 4713

3000

SP1

DMC1

DMR1

CdG3

2

0001 4711

3000

SP2

DMC1

DMR2

CdG1

3

0001 4711

1000

SP3

DMC1

DMR3

CdG1

4

0001 4712

3000

SP3

DMC1

DMR2

CdG2

SAP Extended Warehouse Management (SAP EWM)

510

924

SAP Online Help

20.07.2007

Sample Part of a whole that reflects the quality of the whole and that is to be examined in an inspection.

Structure The sample category describes the use of the sample. The following sample categories exist: •

Primary samples are samples that are taken directly from a material or batch. They are then inspected or used to form pooled samples.

•

Pooled samples are samples that are formed by combining two or more primary samples taken from the same material or batch.

•

Reserve samples are primary samples of a material or batch that are reserved for a later inspection.

Integration If you have assigned a sample-drawing procedure to an inspection rule, the system automatically creates samples when it creates an inspection document based on this inspection rule. You can also create samples manually.

SAP Extended Warehouse Management (SAP EWM)

510

925

SAP Online Help

20.07.2007

Item Subset of the total quantity to be inspected.

An item is used to group units of the inspected material for the further business process. As a rule, subsets are formed as part of this grouping process based on similar grades. You can, for example, group elements that have the same finding in the subset.

Integration An inspection document can contain several items. If you specify a code group for items in the inspection rule, you can valuate the items individually in the inspection document.

Example A 100% inspection is performed for a delivery of apples. Depending on the finding, these apples are divided into subsets according to their grades: •

1A

•

1

•

2

•

Rotten

Their further use - for example, as trading goods, fodder, or compost - is determined when the subset decision is made.

SAP Extended Warehouse Management (SAP EWM)

510

926

SAP Online Help

20.07.2007

Findings Describe deviations from the requirements.

Deviations from the requirements may be observed during quality inspections or spontaneously. You can describe these deviations in findings. You can record findings in the following ways: •

Individual You create a finding for every individual deviation that has been observed.

•

Summarized You enter the number of times a deviation occurred for predefined deviations, or describe the observed deviations in summarized form.

Structure To allow the automatic valuation of findings, you describe findings using codes. These codes are stored in catalogs. Every finding is associated with a finding type. This controls the following: •

The fields that are available to you for creating, changing, and displaying the finding.

•

The fields that require an entry when you are creating a finding.

•

The catalogs you can use to describe the finding and which of these catalogs is the master catalog. In addition to the name of the code, the following data is also copied into the data record of the finding from the master catalog: o

Class of the finding

o

Valuation

o

Indicator that shows documents are assigned to the catalog entry

During summarized recording of findings, the possible codes of master catalog are used. •

Which codes in a catalog are available for describing the finding based on a property value of the inspection document

•

Whether you have to record the finding individually or in summarized form

You define the finding types in Customizing for the Quality Inspection Engine, under Define Finding Types.

Integration In the inspection rule, you define the finding types that are available to you in the respective business processes.

SAP Extended Warehouse Management (SAP EWM)

510

927

SAP Online Help

20.07.2007

A finding cannot be created without reference to an object. You can create findings for the following objects: •

Inspection document

•

Inspection document item

•

Sample

SAP Extended Warehouse Management (SAP EWM)

510

928

SAP Online Help

20.07.2007

Catalog Used to group codes by content. Codes describe qualitative, textual subjects in coded form.

In the Quality Inspection Engine (QIE), you can use codes in catalogs to describe findings.

Integration The QIE uses catalogs in the consumer system. If you have made appropriate settings in the consumer system, you can change the catalogs in the QIE. However, you cannot create any catalogs in the QIE. To allow the QIE to access catalogs in the consumer system, you must make the required settings in Customizing of the QIE under Define Catalogs. Catalog filters control which codes in a catalog are available for describing the finding based on the property value of the inspection document. You can set up a catalog filter so that your users can only use certain codes depending on the material. This is because, for example, different defects will be found when inspecting a computer than when inspecting a pen. You can specify catalog filters in finding types and in inspection rules.

SAP Extended Warehouse Management (SAP EWM)

510

929

SAP Online Help

20.07.2007

Inspection Decision Decision about the acceptance or rejection of the inspected object, for example, the inspection document or the sample.

When you make the inspection decision you are deciding on the basis of the inspection whether the inspected object is accepted or rejected. As soon as the inspection decision has been made, the status Decision Made is set in the inspection document.

Structure You define the decision codes in Customizing of the Quality Inspection Engine (QIE).

SAP Extended Warehouse Management (SAP EWM)

510

930

SAP Online Help

20.07.2007

Archiving - Inspection Documents (CA-QIE) The archiving object QIE_INSP is used for archiving inspection documents and dependent objects in the component Quality Inspection Engine (CA-QIE).

You can use the archiving object QIE_INSP to archive inspection documents and their dependent objects if you no longer require direct access to these. Dependent objects are samples, items, and findings. You can display the archived data in the corresponding display transaction in the consumer system, but you cannot reload the data.

Structure If you use the archiving object QIE_INSP, data from the following tables, among others, is archived: Table to be archived QIE_INSP_DOC

Short description Inspection document

QIE_INSP_DOC_ES Document data for the inspection document in the external system QIE_INSP_DOC_EX Inspection data and results data for the inspection document QIE_INSP_DOC_IX

Index of inspection object properties for the inspection document

QIE_ELEMENT

Elements (samples and items)

QIE_ELEMENT_IX

Index for elements

QIE_FIND_CODE

Additional codes for finding

QIE_FINDING

Findings

QIE_ASSIGN

QIE: Links

QIE_DOC_ASSIGN

Document assignment

The following archiving classes, among others, are involved: Archiving Class

Short Description

QIE_INSP_D

Inspection document

QIE_INSP_E

Elements (samples and items)

QIE_CONF_F

Findings

QIE_DOC_AS

Document assignment

CRM_STATUS

Status objects (GUID-based status management)

SAP Extended Warehouse Management (SAP EWM)

510

931

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

932

SAP Online Help

20.07.2007

Inspections (CA-QIE) During preprocessing, the system checks that: •

The inspection document and its dependent objects are not in processing.

•

The inspection document has the status To Be Archived (I1855) or Cancelled (I1854).

•

The inspection document has none of the above statuses, but it has been completed and the number of days since the last change has expired. You define the number of days in the selection conditions of the report.

•

The checks that you implemented in the Business Add-In (BAdI) Own Checks for Archiving Object QIE_INSP (ARC_QIE_INSP_CHECK) had positive results.

•

The status of the inspection document allows the operations Flag for Archiving (QE07) and Archive (QE09).

SAP Extended Warehouse Management (SAP EWM)

510

933

SAP Online Help

20.07.2007

Application Customizing (CA-QIE) In Application Customizing, you can adjust the settings for the execution of archiving runs. Under Archiving, you can create and activate implementations for the following Business AddIns (BAdIs): •

You can use the BAdI Own Inspections for Archiving Object QIE_INSP (ARC_QIE_INSP_CHECK) to set up additional checks in preprocessing. You can use this BAdI, among other things, to differentiate between the number of days since the last change of the different inspection object types.

•

You can use the BAdI Own Data for Archiving Object QIE_INSP (ARC_QIE_INSP_WRITE) to archive and delete own data. The BAdI is called in the archiving and deletion runs.

SAP Extended Warehouse Management (SAP EWM)

510

934

SAP Online Help

20.07.2007

Preprocessing: Editing Variants (CA-QIE) You can use the preprocessing program to set the status To Be Archived or Archived for inspection documents. This status is a prerequisite for archiving. Note It is not possible to change inspection documents that have the status To Be Archived or Archived. End of the note.

Procedure 1. Choose

Tools Administration Administration Data Archiving

.

2. Enter the archiving object QIE_INSP and confirm your entry. 3. Choose Preprocessing. 4. Enter a report variant on the Preprocessing screen. If no variant exists, choose Maintain to maintain the required variant. If you choose Detailed Log on the selection screen, the system returns a log line for every archived inspection document. 5. Enter the start date and the spool parameters. You use the spool parameters to control the print output of the preprocessing log that is generated. 6. Select Execute on the initial screen. 7. You can access information about the status of the preprocessing job in the job overview. You can also display the log in the job overview after the job has been completed.

Result The preprocessing program sets the status To Be Archived or Archived for inspection documents. The preprocessing program creates a log and, if required, a detailed log. After the preprocessing run, you can archive inspection documents that you have flagged.

SAP Extended Warehouse Management (SAP EWM)

510

935

SAP Online Help

20.07.2007

Writing: Editing Variants (CA-QIE) The archiving program writes the data records of the archiving object QIE_INSP to the archive.

Prerequisites Before you start the archiving run, you must flag inspection documents for archiving using the preprocessing run.

Procedure 1. Choose

Tools Administration Administration Data Archiving

.

2. Enter the archiving object QIE_INSP and choose Write. 3. Enter a report variant on the Create Archive Files screen. If no variant exists, choose Maintain to maintain the required variant. If you choose Detailed Log on the selection screen, the system returns a log line for every archived inspection document. 4. Enter the start date and the spool parameters. You use the spool parameters to control the print output of the archiving log that is generated. 5. Select Execute on the initial screen. 6. You can access information about the status of the archiving job in the job overview. You can also display the log in the job overview after the job has been completed.

Result The data of the selected inspection documents is archived. The archiving program creates a log and, if required, a detailed log. If you specify that the deletion job should start automatically in archiving object-specific Customizing, the system will start the deletion job automatically after archiving has taken place. If the deletion job is not started automatically, you must start it manually.

SAP Extended Warehouse Management (SAP EWM)

510

936

SAP Online Help

20.07.2007

Deleting: Editing Variants (CA-QIE) The deletion program deletes the data records for the archiving object QIE_INSP.

Prerequisites Before you start the deletion run, you must archive the inspection documents using the archiving run.

Procedure 1. Choose

Tools Administration Administration Data Archiving

.

2. On the initial screen of archive administration, enter the archiving object QIE_INSP and choose Delete. 3. On the Execeute Delete Program screen, choose one or more archiving runs using the archive selection. 4. Maintain the start date and the spool parameters. You use the spool parameters to control the print output of the deletion log that is generated. If you choose Detailed Log on the selection screen, the system returns a log line for every archived inspection document. 5. Select Execute on the initial screen. 6. You can access information about the status of the deletion job in the job overview. You can also display the log in the job overview after the job has been completed.

Result The data for the selected archiving runs is deleted. The deletion program creates a log and, if required, a detailed log. You can display the deleted data in the consumer system of the QIE using the corresponding display transactions or using the Archive Explorer.

SAP Extended Warehouse Management (SAP EWM)

510

937

SAP Online Help

20.07.2007

Authorizations (CA-QIE) To display the programs for archiving the archiving object QIE_INSP, you need the authorization S_ARCHIVE. To display the archived data, you need authorization for the Archive Information System or for the display transaction in the consumer system.

SAP Extended Warehouse Management (SAP EWM)

510

938

SAP Online Help

20.07.2007

Log (CA-QIE) When you execute the various archiving programs, the system creates logs in list form. If you execute the programs in the background, the system uses the print output and outputs the logs via spool requests. The logs contain information, for example, about which inspection documents were selected or how many inspection documents were processed.

Prerequisites The logs are output after the preprocessing, archiving, and deletion runs.

Features The system creates different logs for each of the three archiving steps. To display the selection conditions, you may have to select the selection cover sheet in the spool settings.

Preprocessing Log On the selection screen, you can choose between a summarized and a detailed log. The system displays the following information: •

Selection criteria

•

Number of objects in the list of hits that were retrieved based on the selection conditions

•

Number of selected inspection documents for which the status archived can be set

Archiving Log On the selection screen, you can choose between a summarized and a detailed log. For a summarized log, the system displays the following information: •

Selection criteria

•

Key of the archive file and number of the archiving run

•

Statistical key figures for the archived database tables

•

Number of inspection documents to be archived

Deletion Log On the selection screen, you can choose between a summarized and a detailed log. The system displays the following information: •

Indicator for test mode or productive mode

•

Keys of archive files

•

Number of deleted objects

•

Number of deleted records for every relevant database table

If outputting a detailed log, the system also shows the following information for every archived object: SAP Extended Warehouse Management (SAP EWM)

510

939

SAP Online Help •

External number of the inspection document

•

Success or failure messages

20.07.2007

Note You should only select the detailed log for small quantities of data, for example, in test mode for just a few objects. If you select too much data, the system could terminate due to memory overflow. End of the note.

Activities •

You must specify suitable spool parameters before you execute an archiving program.

•

The log is created automatically by the system after the program has been executed.

•

You can display the log using the job overview. You can also display it under Display Spool List Display Contents .

SAP Extended Warehouse Management (SAP EWM)

510

940

SAP Online Help

20.07.2007

Displaying Archived Inspection Documents (CAQIE) You can display archived and deleted inspection documents in the consumer system.

Activities In the consumer system, call the display transaction for inspection documents and enter the number of the archived and deleted inspection document. You can also use the Archive Explorer to access the technical view of the archived inspection document.

SAP Extended Warehouse Management (SAP EWM)

510

941

SAP Online Help

20.07.2007

Quality Inspection Engine (QIE) Security Guide

SAP Extended Warehouse Management (SAP EWM)

510

942

SAP Online Help

20.07.2007

Introduction This guide does not replace the daily operations handbook that we recommend customers create for their specific productive operations.

Target Audience ●

Technology consultants

●

System administrators

This document is not included as part of the installation guides, configuration guides, technical operation manuals, or upgrade guides. Such guides are only relevant for a certain phase of the software life cycle, whereas security guides provide information that is relevant for all life-cycle phases.

Why Is Security Necessary? With the increasing use of distributed systems and the Internet for managing business data, the demands on security are also on the rise. When using a distributed system, you need to be sure that your data and processes support your business needs without allowing unauthorized access to critical information. User errors, negligence, or attempted manipulation on your system should not result in loss of information or processing time. These demands on security also apply to the Quality Inspection Engine (QIE) component. To assist you in securing the QIE component, we provide this security guide.

About this Document The security guide provides an overview of the security-relevant information that applies to the QIE component. Since the QIE component is based on the Web Application Server (Web AS), this guide only describes topics that vary from what is described in the security guide for the Web AS. Therefore we strongly recommend that you also consult the SAP Web AS Security Guide on the SAP Service Marketplace at service.sap.com/securityguide → SAP NetWeaver '04 Component Security Guides → SAP Web AS Security Guide ABAP and JAVA. Overview of the Main Sections The Security Guide comprises the following main sections: ●

Before You Start This section contains information about why security is necessary, how to use this document, and references to other security guides that are the foundation for this security guide.

●

Technical System Landscape This section provides an overview of the technical components and communication paths that are used by the QIE component.

●

User Administration and Authentication This section provides an overview of the following user administration and authentication aspects: ○

Recommended tools for user management.

○

User types that are required by the QIE component.

SAP Extended Warehouse Management (SAP EWM)

510

943

SAP Online Help

●

20.07.2007

○

Standard users that are delivered with the QIE component.

○

Overview of the user synchronization strategy, if several components or products are involved.

○

Overview of how integration into Single Sign-On environments is possible.

Authorizations This section provides an overview of the authorization concept that applies to the QIE component.

●

Network and Communication Security This section provides an overview of the communication paths used by the QIE component and the security mechanisms that apply. It also includes our recommendations for the network topology to restrict access at the network level.

●

Data Storage Security This section provides an overview of any critical data that is used by the QIE component and the security mechanisms that apply.

●

Security for Third-Party or Additional Applications This section provides security information that applies to third-party or additional applications that are used with the QIE component.

●

Dispensable Functions with Impacts on Security This section provides an overview of functions that have impacts on security and can be disabled or removed from the system.

●

Other Security-Relevant Information This section contains information about using a Web browser for the user interface.

●

Trace and Log Files This section provides an overview of the trace and log files that contain securityrelevant information, to enable you, for example, to reproduce activities if a security breach does occur.

●

Appendix This section provides references to further information.

SAP Extended Warehouse Management (SAP EWM)

510

944

SAP Online Help

20.07.2007

Before You Start Fundamental Security Guides The Quality Inspection Engine (QIE) component is based on the Web Application Server (Web AS). Therefore, the corresponding Security Guides also apply to the QIE component. Pay particular attention to the most relevant sections or specific restrictions as indicated in the table below. Fundamental Security Guides Scenario, Application or Component Security Guide

Most relevant Sections or Specific Restrictions

SAP Web AS

SAP NetWeaver Security Guide SAP Web AS Security Guide

For a complete list of the available SAP Security Guides, see the SAP Service Marketplace at service.sap.com/securityguide.

Important SAP Notes The most important SAP Notes that apply to the security of QIE are shown in the table below. Important SAP Notes SAP Note Number

Title

Comment

736556

Security Guide: Quality Inspection Engine

The note covers all problems discovered after the publication of the security guide and additional information about security issues.

Additional Information For more information about specific topics, see the following quick links: Quick Links to Additional Information Content

Quick Link on the SAP Service Marketplace

Security

service.sap.com/security

Security Guides

service.sap.com/securityguide

Related SAP Notes

service.sap.com/notes

Released Platforms

service.sap.com/platforms

Network Security

service.sap.com/securityguide

SAP Solution Manager

service.sap.com/solutionmanager

SAP Extended Warehouse Management (SAP EWM)

510

945

SAP Online Help

20.07.2007

Technical System Landscape Use The QIE Add-On is installed on the ABAP engine of a SAP Web Application Server. QIE only communicates with components of the Web AS of the same system. For more information about the technical system landscape, see the resources listed in the table below. More Information about the Technical System Landscape Topic

Guide/Tool

Quick Link to SAP Service Marketplace

Technical description of QIE and the underlying technological components such as SAP NetWeaver

Master Guide

service.sap.com/instguides

Security

SAP Extended Warehouse Management (SAP EWM)

service.sap.com/security

510

946

SAP Online Help

20.07.2007

User Administration and Authentication The Quality Inspection Engine (QIE) employs the user management and authentication mechanisms provided with the SAP NetWeaver platform, in particular the SAP Web Application Server ABAP. Therefore, the security recommendations and guidelines for user administration and authentication as described in the SAP Web AS Security Guide for ABAP Technology also apply to QIE. You can find this security guide on the SAP Service Marketplace at sap.service.com/securityguide → SAP NetWeaver '04 Component Security Guides → SAP Web AS Security Guide ABAP and JAVA.

SAP Extended Warehouse Management (SAP EWM)

510

947

SAP Online Help

20.07.2007

User Management Use User management for the Quality Inspection Engine (QIE) employs the mechanisms provided by the SAP Web Application Server ABAP, for example, tools, user types, and password policies. For an overview of how these mechanisms apply to QIE, see the sections below. In addition, we provide a list of the standard users required for operating QIE.

User Administration Tools The table below shows the tools for user management and user administration in QIE. User Management Tools Tool

Detailed Description

User and role maintenance with SAP Web AS ABAP (Transactions SU01, PFCG)

For more information, see Users and Roles [Extern] (BC-SEC-USR)

Prerequisites

User Types It is often necessary to specify different security policies for different types of users. For example, your policy may specify that individual users who perform tasks interactively have to change their passwords on a regular basis, but not those users who run background processing jobs. The user types that are required for QIE include: ●

Individual users: dialog users are used for QIE Customizing.

For more information, see User Types [Extern] in the SAP Web AS ABAP Security Guide.

Standard Users QIE does not require any specific standard users.

SAP Extended Warehouse Management (SAP EWM)

510

948

SAP Online Help

20.07.2007

Integration into Single Sign-On Environments Use The Quality Inspection Engine (QIE) supports the Single Sign-On (SSO) mechanisms provided by the SAP Web Application Server ABAP. Therefore, the security recommendations and guidelines for user administration and authentication as described in the SAP Web Application Server Security Guide [Extern] also apply to QIE. The supported mechanisms are listed below. Secure Network Communications (SNC) SNC is available for user authentication and provides for an SSO environment when using the SAP GUI for Windows or Remote Function Calls. For more information, see Secure Network Communications (SNC) [Extern] in the SAP Web Application Server Security Guide. SAP Logon Tickets QIE supports the use of logon tickets for SSO when using a Web browser as the front-end client. In this case, users can be issued a logon ticket after they have authenticated themselves on the initial SAP system. The ticket can then be submitted to other systems (SAP or external systems) as an authentication token. The user does not need to enter a user ID or password for authentication but can access the system directly after the system has checked the logon ticket. You can find more information under SAP Logon Tickets [Extern] in the SAP Web Application Server Security Guide. Client Certificates As an alternative to user authentication with a user ID and passwords, users with a Web browser as a front-end client can also provide X.509 client certificates for authentication purposes. In this case, user authentication is performed on the Web server using the Secure Sockets Layer Protocol (SSL Protocol) and no passwords have to be transferred. User authorizations are valid in accordance with the authorization concept in the SAP system. You can find more information under Client Certificates [Extern] in the SAP Web Application Server Security Guide.

SAP Extended Warehouse Management (SAP EWM)

510

949

SAP Online Help

20.07.2007

Authorizations Use The Quality Inspection Engine (QIE) uses the authorizations provided by the SAP Web Application Server. Therefore, the recommendations and guidelines for authorizations as described in the SAP Web AS Security Guide ABAP also apply to QIE. The SAP Web Application Server authorization concept is based on assigning authorizations to users based on roles. For role maintenance, use the profile generator (transaction PFCG) on the SAP Web AS ABAP, and the User Management Engine’s user administration console for SAP Web AS Java.

Standard Roles QIE does not deliver its own user roles.

Standard Authorization Objects The table below shows the security-relevant authorization objects that are used by QIE: Standard Authorization Objects Authorization Objects

Field

Value

Description

QIE_INSPDO

ACTVT

01, 02, 03, 75

Activity

QIE_OBJTYP

*

Business object type

QIE_OWNER

*

Owning software component

QIE_PROCES

*

Process

QIE_AUTHGR

*

Authority group

ACTVT

01, 02, 03, 06

Activity

QIE_OBJTYP

*

Business object type

QIE_OWNER

*

Owning software component

QIE_PROCES

*

Process

ACTVT

01, 02, 03,

Activity

QIE_OBJTYP

*

Business object type

QIE_OWNER

*

Owning software component

QIE_PROCES

*

Process

ACTVT

01, 02, 03, 06

Activity

QIE_SDRW_T

*

Sample drawing type

ACTVT

01, 02, 03, 75, 85

Activity

QIE_E_SCAT

*

Element subcategory

QIE_E_CAT

*

Element category

QIE_E_TYPE

*

Element type

ACTVT

01, 02, 03, 06

Activity

QIE_IRULE

QIE_QLVL

QIE_SDRW

QIE_ELEM

QIE_FIND

SAP Extended Warehouse Management (SAP EWM)

510

950

SAP Online Help

20.07.2007

QIE_FIN_TY

*

SAP Extended Warehouse Management (SAP EWM)

Finding type

510

951

SAP Online Help

20.07.2007

Network and Communication Security Your network infrastructure is extremely important in protecting your system. Your network needs to support the communication necessary for your business needs without allowing unauthorized access. A well-defined network topology can eliminate many security threats based on software flaws (at both the operating system and application level), or network attacks such as eavesdropping. If users cannot log on to your application or database servers at the operating system or database layer, then there is no way for intruders to compromise the machines and gain access to the backend system’s database or files. Additionally, if users cannot connect to the server LAN (local area network), they cannot exploit well-known bugs and security holes in network services on the server machines. The network topology for the Quality Inspection Engine (QIE) is based on the topology used by the SAP NetWeaver platform. Therefore, the security guidelines and recommendations described in the SAP NetWeaver Security Guide also apply to QIE. Details that specifically apply to QIE are described in the following topics: ●

Communication Channel Security [Seite 953] This topic describes the communication paths and protocols used by QIE.

●

Network Security [Seite 954] This topic describes the recommended network topology for QIE. It shows the appropriate network segments for the various client and server components and where to use firewalls for access protection. It also includes a list of the ports needed to operate QIE.

●

Communication Destinations [Seite 955] This topic describes the information needed for the various communication paths, for example, which users are required for which communication paths.

For more information, see the following sections in the SAP NetWeaver Security Guide: ●

Network and Communication Security

●

Security Aspects for Connectivity and Interoperability

SAP Extended Warehouse Management (SAP EWM)

510

952

SAP Online Help

20.07.2007

Communication Channel Security Use Communication channels transfer your business data in all its different forms, therefore, you should protect these channels against unauthorized access. SAP offers general recommendations and technologies to protect your system landscape based on SAP NetWeaver. For information about: ●

Communication security for SAP NetWeaver, see the SAP NetWeaver Security Guide on the SAP Service Marketplace at service.sap.com/securityguide → SAP NetWeaver Network and Communication Security.

●

Security aspects for the connectivity and interoperability of SAP NetWeaver, see the SAP NetWeaver Security Guide on the SAP Service Marketplace at service.sap.com/securityguide → SAP NetWeaver Connectivity Security Guide.

●

Communcation channel security for SAP Exchange Infrastructure (SAP XI), consult the SAP Exchange Infrastructure (SAP XI) Security Guide on the SAP Service Marketplace at service.sap.com/securityguide → SAP NetWeaver Component Security Guides → SAP Exchange Infrastructure Security Guide.

The following table shows the communication paths used by the Quality Inspection Engine (QIE), the protocol used for the connection, and the type of data transferred. Communication Paths Communication Path

Protocol Used

Type of Data Transferred

Data Requiring Special Protection

Front-end client using SAP GUI for Windows to application server

DIAG

All customizing data

Passwords

Front-end client using a Web browser to application server (SAP GUI for HTML)

HTTP

All customizing data

Passwords

Application server to application server

RFC, XI

All application data

Passwords and business data

DIAG and RFC connections can be protected using Secure Network Communications (SNC). HTTP connections are protected using the Secure Sockets Layer (SSL) protocol. For more information, see Transport Layer Security [Extern] in the SAP NetWeaver Security Guide

SAP Extended Warehouse Management (SAP EWM)

510

953

SAP Online Help

20.07.2007

Network Security Use Your network infrastructure is extremely important in protecting your system. A well-defined network topology can eliminate many security threats based on software flaws (at both the operating system and application level) or network attacks such as eavesdropping. SAP offers general recommendations to protect your system landscape based on SAP NetWeaver.

For information about the network security of SAP NetWeaver, see the SAP NetWeaver Security Guide on the SAP Service Marketplace at service.sap.com/securityguide → SAP NetWeaver Network and Communication Security.

A minimum security demand for your network infrastructure is the use of a firewall for all your services provided via the Internet. A more secure variant is to protect your systems (or groups of systems) by locating the different "groups" in different network segments, each protected against unauthorized access with a firewall. (Note: external security attacks can also come from "inside" if the intruder has already taken over control of one of your systems.)

For information about access control using firewalls, see the SAP NetWeaver Security Guide on the SAP Service Marketplace at service.sap.com/securityguide → SAP NetWeaver Security Guide → Network and Communication Security - Using Firewall Systems for Access Control.

SAP Extended Warehouse Management (SAP EWM)

510

954

SAP Online Help

20.07.2007

Communication Destinations The following is an overview of the communication destinations used for the Quality Inspection Engine:

None of the destinations listed are delivered.

Destination

Type

Description

QIE -> external system

SAP XI

SAP XI Configuration Guide under Connecting Business Systems with an Integration Engine to the Central Integration Server → Creating a Connection Between a Business System and the System Landscape Directory (SLD)

External system -> QIE

SAP XI

SAP XI Configuration Guide, as above

All of the users have the necessary QIE authorizations. For more information, see the section Authorizations [Seite 950]. The SAP XI configuration guide is on the SAP Service Marketplace at service.sap.com/instguides → SAP NetWeaver → Installation → SAP XI

SAP Extended Warehouse Management (SAP EWM)

510

955

SAP Online Help

20.07.2007

Data Storage Security Use The data storage security of SAP NetWeaver and components installed on this base is described in detail in the SAP NetWeaver Security Guide.

For information about the data storage security of SAP NetWeaver, see the SAP Service Marketplace at service.sap.com/securityguide → SAP NetWeaver DB and OS Platform Security Guides. All business data for the QIE component is stored in the system database. This business data is protected by the authorization concept of SAP NetWeaver.

SAP Extended Warehouse Management (SAP EWM)

510

956

SAP Online Help

20.07.2007

Security for Additional Applications Use There are no relevant third-party applications.

SAP Extended Warehouse Management (SAP EWM)

510

957

SAP Online Help

20.07.2007

Other Security-Relevant Information Web Browser as User Front End To access QIE Customizing with a Web browser (SAP GUI for HTML ) as the user front end, it is necessary to activate Java Script (Active Scripting) to ensure a working user interface. Note that this could conflict with your security policy regarding Web services!

SAP Extended Warehouse Management (SAP EWM)

510

958

SAP Online Help

20.07.2007

Trace and Log Files Use Trace and log files are written by the individual SAP NetWeaver components.

For information about trace and log files in SAP NetWeaver, see the SAP Service Marketplace at service.sap.com/securityguide → SAP NetWeaver Security Guide. Within the bounds of these standard mechanisms, the Quality Inspection Engine automatically creates change documents each time a user changes important business data. In addition, you can define that each time a user makes a change in Customizing for QIE, the system creates a change document.

SAP Extended Warehouse Management (SAP EWM)

510

959

SAP Online Help

20.07.2007

Appendix You can find more information about the security of SAP applications on the SAP Service Marketplace, at service.sap.com/security. Security guides are available at service.sap.com/securityguide.

Related Information For more information about topics related to security, see the quick links shown in the table below. Quick Links to Related Information Content

Quick Link on the SAP Service Marketplace (service.sap.com)

Master Guides, Installation Guides, Upgrade Guides, Solution Management Guides

instguides ibc

Related SAP Notes

notes

Released Platforms

platforms

Network Security

securityguide

SAP Solution Manager

solutionmanager

SAP Extended Warehouse Management (SAP EWM)

510

960

SAP Online Help

20.07.2007

Customs Procedure Use Extended Warehouse Management (EWM) offers integration with SAP Global Trade Services (SAP GTS) to process the import and export of goods. You can perform the following customs procedures: ●

Transit procedure [Seite 215]

●

Safekeeping [Seite 962]

●

Customs warehousing procedure [Seite 964]

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

SAP Extended Warehouse Management (SAP EWM)

510

961

SAP Online Help

20.07.2007

Safekeeping Purpose Safekeeping is a customs procedure that begins, in most cases, automatically after completion of the transit procedure [Seite 215] when you have received unloading permission from SAP Global Trade Services (SAP GTS), and you post goods receipt. The goods remain in safekeeping until the employees in SAP GTS have made a decision about their subsequent use. For example, are you to import the goods and pay customs duties and taxes, or are the goods to be included in the customs warehousing procedure [Seite 964]?

Prerequisites ●

You have defined a GTS system for the warehouse number in Customizing for Extended Warehouse Management (EWM) under Extended Warehouse Management ( Interfaces ( GTS Integration ( Define GTS System for Warehouse Number.

●

You have set the Customs Block indicator for the relevant previous document types in Customizing for EWM under Interfaces ( GTS Integration ( Define Previous Document Types. In Germany, the relevant previous document types are T- and T1, for example.

●

You have defined stock types with the role Customs Blocked Stock in Customizing for EWM under Master Data ( Product ( Define Stock Types. All stock types that begin with C are delivered in the standard system.

Process 1. A previous document type exists as the reference document in the inbound delivery, and this previous document type is relevant to customs block. You post goods receipt for this inbound delivery. EWM transfers this data via the ERP system to SAP GTS. The goods are now in safekeeping and have a stock type with the role customs blocked stock [Extern]. During this time, use of the goods is not permitted You can, however, put away the goods and move them in the warehouse. The stock type serves to separate the goods from the normal stock on a logical level. It is not necessary to physically separate the goods in the warehouse. The following goods movements and activities are not permitted: ○

Posting goods issue or creating loading warehouse tasks in the goods issue process

○

Stock changes except for changes to the availability in the case of putaway within customs blocked stock

○

Initial entry of stock balances

○

Scrapping

○

Clearing differences to the ERP system in the Difference Analyzer [Seite 677]

○

Quality check for inbound deliveries

○

Performing certain activities for value-added services (VAS)

You can use the Business Add-In (BAdI) Stock Checks for Goods Movements (/SCWM/EX_CORE_GM_STOCK) to define additional restrictions for goods movements.

SAP Extended Warehouse Management (SAP EWM)

510

962

SAP Online Help

20.07.2007

2. The employees in SAP GTS check the customs conditions for the goods and send the release to EWM via tRFC. EWM automatically makes a posting change for the goods to normal stock. You can put away the goods either before or after the release.

If SAP GTS sends the release immediately, the safekeeping is short, in other words, simply for the time required for communication with the customs authority.

EWM releases the customs block stock as soon as the notification arrives, unless the customs blocked stock is blocked by an open warehouse task (for example, a putaway warehouse task). In this case, you must start the release again later on. You must schedule the report /SCWM/GTS_CBREL_MON in the background to postprocess such messages.

If you have picked the quantity for the outbound delivery from the customs blocked stock, you can stop invoicing before goods issue [Seite 368] by using the following Business Add-Ins (BAdIs):

ƒ

S&R Activities for a Transportation Unit (/SCWM/EX_SR_ACTION_TU)

ƒ

S&R Activities for a Vehicle (/SCWM/EX_SR_ACTION_VEH)

These enable you to release the customs blocked stock before the system generates the invoice. See also: Connection of Delivery Processing to Safekeeping [Seite 220]

SAP Extended Warehouse Management (SAP EWM)

510

963

SAP Online Help

20.07.2007

Customs Warehousing Procedure Use You can process this customs procedure in SAP Global Trade Services (SAP GTS). Since the stocks are in normal stock, it does not have an effect on the processes in the warehouse. The only exception is scrapping. For more information, see Scrapping as Part of the Customs Warehousing Procedure [Seite 965]. Extended Warehouse Management (EWM) automatically communicates deliveries and goods movements to SAP GTS via the ERP system. In EWM, it is not known whether the goods are duty-paid goods or duty-unpaid goods. Only SAP GTS that has its own inventory management has this information. For more information about the customs warehouse in SAP GTS, see the SAP Library under SAP xAPPs → SAP Global Trade Services → SAP Customs Management → Customs Procedure with Economic Impact → Customs Warehouse.

Prerequisites ●

You have defined a GTS system for the warehouse number in Customizing for Extended Warehouse Management (EWM) under Extended Warehouse Management → Interfaces → GTS Integration → Define GTS System for Warehouse Number.

●

You have defined a customs ID in Customizing for EWM under Extended Warehouse Management → Interfaces → GTS Integration → Define Customs ID.

●

You have assigned the warehouse number and the party entitled to dispose to the customs ID. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Settings → Assign Warehouse Number/Party Entitled to Dispose to Customs ID.

●

You have distributed the products that are part of the customs warehousing procedure in the customs ID from SAP GTS to EWM. For more information, see the SAP Library under SAP xAPPs → SAP Global Trade Services → SAP Customs Management → Master Data for SAP Customs Management → Distr. of Prod. Chars for Special Customs Procds in Feeder Systs.

See also: Connection of Delivery Processing to Customs Warehousing Procedure [Seite 221]

SAP Extended Warehouse Management (SAP EWM)

510

964

SAP Online Help

20.07.2007

Scrapping as Part of the Customs Warehousing Procedure Use You can perform scrapping in a planned or unplanned way as part of the customs warehousing procedure: ●

Unplanned scrapping (duty-unpaid stock) The scrapping of duty-unpaid stock requires permission from the customs authority. You can, however, scrap the stock without this permission but in this case you have to pay customs duties and taxes.

●

Planned scrapping (duty-paid stock) In the case of planned scrapping, you do not have to pay customs duties or taxes. However, as a prerequisite you must have been given permission by the customs authority. The customs authority can react as follows: ○

Scrapping is permitted.

○

Scrapping is permitted, but the customs authority reserves the right to send an employee to be present when the stock is scrapped.

After the stock has been moved to the scrapping area, it is given a stock type with the role scrap stock [Extern].

You can use the Business Add-In (BAdI) Stock Checks for Goods Movements (/SCWM/EX_CORE_GM_STOCK) to define restrictions for goods movements involving scrap stock.

Prerequisites To ensure that Extended Warehouse Management (EWM) automatically posts the goods to scrap stock when they are moved to the scrapping area, you have made the following settings: ●

You have defined stock types with the role Scrapping Stock in Customizing for Extended Warehouse Management (EWM) under Extended Warehouse Management → Master Data → Product → Define Stock Types. All stock types that begin with S are delivered in the standard system.

●

You have defined a storage type Scrapping Zone with the following attributes in Customizing for EWM under Extended Warehouse Management → Master Data → Define Storage Type: In the Goods Movement Control area, you have chosen Blocked Stock (BB) as the nondependent stock type and Scrapping Stock (S) as the stock type role.

Activities You create a posting change delivery for scrapping in EWM, or EWM has automatically created a posting change request for a posting change delivery for scrapping from the ERP system. If the product is relevant to customs warehousing, the delivery is locked until you have received a scrapping reference number from SAP Global Trade Services (SAP GTS). See also: Scrapping [Seite 366]

SAP Extended Warehouse Management (SAP EWM)

510

965

SAP Online Help

20.07.2007

Performing Scrapping [Seite 130]

SAP Extended Warehouse Management (SAP EWM)

510

966

SAP Online Help

20.07.2007

EH&S Services Use The functions in EH&S Services support you with the safe handling and storage of hazardous substances and with the transport of dangerous goods in accordance with regulations.

Features The following functions are available in EH&S Services: ●

In phrase management [Seite 968] you can enter texts that have a standard character in the form of phrases with little effort required for entry and translation.

●

In the hazardous substance master [Seite 969] you can enter all important data relating to hazardous substances, for example, data that you require for hazardous substance checks prior to storage.

●

In the inventory list of hazardous substances for the fire department [Seite 971] you can extract all the important data that the fire department requires in the case of a fire.

●

In dangerous goods management [Seite 973] you can enter all the important data for dangerous goods. With this data, you can run dangerous goods checks, for example, or print dangerous goods data on a delivery note.

SAP Extended Warehouse Management (SAP EWM)

510

967

SAP Online Help

20.07.2007

Phrase Management Use This function supports the central management and translation of text modules called phrases [Extern]. You can use phrases to perform the following language-independent activities: ●

Record information about hazardous substances in the hazardous substance master, for example, R and S phrases

●

Output dangerous goods texts on dangerous goods documents

Phrases are managed in phrase libraries, from which you select one library for editing data.

Features For more information about the individual functions of phrase management, see the documentation for SAP ERP 2005 in SAP Help Portal under SAP ERP Central Component → Logistics → Environment, Health and Safety (EHS) → Basic Data and Tools (EHS-BD) → Phrase Management (EHS-BD-PHR). The following functions are not supported in phrase management in EH&S Services: ●

Use of phrases in the value assignment of specifications and in EH&S reports

●

Import and export of phrases

●

Phrase merging

●

Phrase combining

●

Master data matchup

●

Data exchange via ALE

Activities You can access the phrase management functions on the SAP Easy Access screen, under SCM Basis → EH&S Services → Phrase Management.

SAP Extended Warehouse Management (SAP EWM)

510

968

SAP Online Help

20.07.2007

Hazardous Substance Master Use With this function, you create and edit hazardous substance master records.

Integration The system uses the data in the hazardous substance master records, for example, in the following places: ●

The system outputs hazardous substance texts in Extended Warehouse Management in radio frequency transactions (RF transactions, see Radio Frequency Framework [Seite 781]) and on warehouse tasks [Seite 405]. In Customizing for Extended Warehouse Management in the IMG activity Assign Activities to Text Types, you specify the text type to whichthese hazardous substance texts must belong so that the system can display them in a specific activity.

The displayed hazardous substance texts can be R and S phrases, for example. ●

By means of the putaway checks and putaway strategies [Seite 375] in Extended Warehouse Management, the system makes sure that hazardous substances are stored correctly and safely. For this, you specify in Customizing for Extended Warehouse Management in the IMG activities Assign Permitted Hazard Rating 1 for Each Storage Type and Assign Permitted Hazard Rating 2 for Each Storage Type which hazard ratings are permitted in the various storage types. If a hazardous substance has a different hazard rating from that permitted, it cannot be stored in a warehouse of that storage type. The system takes the hazard rating from the hazardous substance master record for the hazardous substance. In the SAP menu, by choosing Extended Warehouse Management → Master Data → Hazardous Substance → Block Storage Type for Hazard Rating 1 or Block Storage Type for Hazard Rating 2, you can also specify that hazardous substances of a permitted hazard rating cannot be put away in a specific warehouse temporarily.

As hazard rating, you can specify the water pollution class in the hazardous substance master records, for example. ●

The system outputs hazardous substance data in the inventory list of hazardous substances for the fire department [Seite 971].

If you want to specify text information in the hazardous substance master in the form of phrases [Extern], you must create these phrases in phrase management [Seite 968].

Features For more information about the individual functions of the Hazardous Substance Master, see the documentation for SAP ERP 2005 in SAP Help Portal under SAP ERP Central Component → Logistics → Environment, Health and Safety (EHS) → Hazardous Substance Management (EHS-HSM) → Hazardous Substance Master. The following functions are not supported in the hazardous substance master in EH&S Services: ●

Filling of the hazardous substance master from specification management

●

Distribution of the hazardous substance master via Application Link Enabling (ALE) from the system containing EH&S Services to other systems

SAP Extended Warehouse Management (SAP EWM)

510

969

SAP Online Help

20.07.2007

An import of data from a central ERP system into the hazardous substance master in EH&S Services via ALE is possible, however. You can also create hazardous substance master data manually in the hazardous substance master in EH&S Services.

Activities To edit hazardous substance master data, on the SAP Easy Access screen, choose SCM Basis → EH&S Services → Hazardous Substance Management → Hazardous Substance Master → Edit Hazardous Substance Master.

SAP Extended Warehouse Management (SAP EWM)

510

970

SAP Online Help

20.07.2007

List of Hazardous Substances for Fire Department Use With this function, you produce an inventory list of hazardous substances for the fire department containing all the important data. This data includes R and S phrases, the water pollution class, the state of matter, and the storage location and storage quantity of the hazardous substance. This enables the fire department to fight fires safely, and helps to prevent accidents caused by the use of the wrong extinguishing agents.

SAP emphasizes that this function is only an example for the output of a fire department list. SAP does not guarantee that the fire department list produced contains all data that is required by the laws in a particular jurisdiction, for example, the European Seveso II Directive (96/82/EC).

Features As the requirements for the data that must appear in the fire department list are different from country to country and company to company, you can adapt the fire department list in Customizing to suit your needs as follows: ●

In Customizing for the Hazardous Substance Master under Specify Text Types and Specify Numeric Value Types, you can specify from which fields and in which order the system is to take hazardous substance data to appear in the fire department list. Under Specify Text Types you can also specify for each relevant field whether the text information that exists as phrases [Extern] is to be listed as phrase texts or phrase codes.

●

In Customizing for Extended Warehouse Management, you can use the Business Add-In (BAdI) Inventory List of Hazardous Substances for Fire Department to adapt the fire department list to suit your requirements in more detail.

Before the fire department list is displayed, you can specify the following: ●

The warehouse for which the fire department list is required

●

Storage types and fire-containment sections [Extern] for which the hazardous substance data is output If you do not enter a storage type or fire-containment section, the system determines the data for all storage types and all fire-containment sections in the warehouse.

●

Unit of measure in which the hazardous substance data is listed If you do not enter a unit of measure, the system uses the default unit for the warehouse.

In the standard system, the system outputs the fire department list to a table and creates a row for each hazardous substance per storage type and fire-containment section selected. Hazardous substances are products for which the Haz. Sub. Strg-Rel. indicator is set in the product master in the Storage view. For each hazardous substance, the system lists the following data from left to right: ...

1. Product data, storage data, and stock data 2. Data from the fields for which you entered a sort sequence for the fire department list in the Sort field in the IMG activity Specify Numeric Value Types 3. Data from the fields for which you entered a sort sequence for the fire department list in the Sort field in the IMG activity Specify Text Types

SAP Extended Warehouse Management (SAP EWM)

510

971

SAP Online Help

20.07.2007

Activities To display the fire department list, proceed as follows: ...

1. On the SAP Easy Access screen, choose Extended Warehouse Management → Monitoring → List of Hazardous Substances for Fire Department. 2. Enter the required data and choose

with the quick info text Execute.

SAP Extended Warehouse Management (SAP EWM)

510

972

SAP Online Help

20.07.2007

Dangerous Goods Management Use With this function, you create and edit dangerous goods master records. The system uses the data in the dangerous goods master records, for example, in the dangerous goods checks and for printing dangerous goods documents.

Integration Dangerous goods management supports you in the following processes: ●

Delivery processing with the Routing Guide The Routing Guide determines and assesses trips for transportation. This includes the selection of a means of transport for each leg of a trip and a list of carriers. With the Routing Guide, you can perform dangerous goods checks to confirm that a trip is safe from a dangerous goods regulation perspective. Delivery processing makes use of the Routing Guide for the following events: ○

When changing a route that was already determined and checked

○

When changing the quantities in an item

○

When changing the product in an item

○

When changing the delivery date

○

A delivery split

You make the settings for this in Customizing for Extended Warehouse Management under Goods Issue Process → Transportation Management → Route Determination and Extended Warehouse Management → Business AddIns (BAdIs) for Extended Warehouse Management → Goods Issue Process → Transportation Management → Route Determination. You can perform the dangerous goods checks in the Routing Guide as part of the Global Available-to-Promise check (GATP check) or simulate them for test purposes by choosing Extended Warehouse Management → Master Data → Shipping and Receiving → Route Determination → Simulate Route Determination. ●

Retrieving dangerous goods data for printing delivery notes [Seite 143] Retrieving, checking, and formatting the dangerous goods data is encapsulated in the BAdI /SCWM/GET_DG_PRINT. The active BAdI implementation /SCWM/EHS_DGDATA_GET is supplied with the standard system. You can adapt the default behavior of the method GET_DG to suit your own requirements.

The following settings are necessary to use dangerous goods management: ●

To integrate the dangerous goods checks in route determination and route checking in the Routing Guide and in delivery note printing, you must process Customizing for EH&S Services.

●

Enter a means of transport in Customizing for Advanced Planning and Optimization in the IMG activity Maintain Means of Transport.

A means of transport must always be assigned to a dangerous goods mode-oftransport category so that the dangerous goods checks can be performed.

SAP Extended Warehouse Management (SAP EWM)

510

973

SAP Online Help ●

20.07.2007

Create routes and legs. In the route header, you can use the DG Check indicator to specify whether dangerous goods checks are to be performed for this route. In addition to this indicator, you can define the dangerous goods group for this route. The dangerous goods group can be one of the following: ○

SPACE/Initial:

Route for dangerous goods and nondangerous goods

○

1

Route for dangerous goods only

○

2

Route for nondangerous goods only

The indicator and the dangerous goods group are evaluated by the Routing Guide, which then calls the dangerous goods checks if required. ●

Using the BAdI /SCTM/EHSDG_BADI_01 BAdI: Dangerous Goods Enhancements for Route Determination (EHS) in Customizing for Extended Warehouse Management, you can define enhancements for the dangerous goods checks in route determination. The BAdI is supplied with a default implementation and enables you to do the following: ○

Consistency checks of header data

○

Consistency checks of item data

○

Consistency checks of transit stages

○

Mapping and filtering of header data

○

Mapping and filtering of item data

○

Mapping and filtering of transit stages

If you want to specify text information in the dangerous goods master in the form of phrases [Extern], you must create these phrases in phrase management [Seite 968].

Features For more information about the individual functions of Dangerous Goods Management, see the SAP Help Portal under SAP R/3 and R/3 Enterprise → SAP R/3 Enterprise Release 4.70 SR1 → SAP R/3 Enterprise Application Components → Logistics → EH&S - Environment, Health and Safety → EH&S Dangerous Goods Management. The following functions are not supported in Dangerous Goods Management in EH&S Services: ●

Dangerous goods basic data

●

Filling

●

Distribution (sending)

●

Template and one-time material processing

●

Data record split from the dangerous goods master screen

●

Printing the dangerous goods master

●

Packaging data

An import of data from other systems into the dangerous goods master in EH&S Services via ALE is possible, however. You can also create dangerous goods data manually in the dangerous goods master in EH&S Services.

SAP Extended Warehouse Management (SAP EWM)

510

974

SAP Online Help

20.07.2007

Activities You can access the functions in Dangerous Goods Management on the SAP Easy Access screen, under SCM Basis → EH&S Services → Dangerous Goods Management.

SAP Extended Warehouse Management (SAP EWM)

510

975

SAP Online Help

20.07.2007

General Functions Use The following documents contain information about general functions in Extended Warehouse Management (EWM).

SAP Extended Warehouse Management (SAP EWM)

510

976

SAP Online Help

20.07.2007

Interfaces Use Extended Warehouse Management (EWM) provides you with various interfaces which you can use to copy external data, for example.

Features The interfaces in EWM give you the following options: ●

Transfer Stock Data [Seite 979]

●

Transfer Storage Bin or Storage Bin Sorting [Seite 978]

SAP Extended Warehouse Management (SAP EWM)

510

977

SAP Online Help

20.07.2007

Transfer Storage Bin or Storage Bin Sorting Use There are two ways to copy existing data: ●

By uploading a local file, such as a Comma-Separated-Values file (CSV file).

●

By uploading a file from an application server. In this case, Extended Warehouse Management (EWM) uses a connection to the Legacy System Migration Workbench [Extern] (LSMW). For more information about the LSMW, see SAP Library under mySAP ERP → SAP Oil & Gas → SAP Oil & Gas (ISOil Downstream) → Integration of SAP Oil & Gas with SAP CRM → F&A Pricing in Integration with SAP CRM → Legacy System Migration Workbench.

Prerequisites You have defined all the master data that is required for creating a storage bin, such as storage types or storage sections. In Customizing for EWM, choose Master Data.

Procedure ...

1. From the SAP Easy Access menu, choose Extended Warehouse Management → Interfaces → Load Storage Bins or Load Storage Bin Sorting. 2. Specify the location from which you want to upload the file: ○

From a local computer

○

From an application server

3. Enter the file name and choose Upload. EWM uploads the file and displays it to you on the tab page Loaded Storage Bins or Loaded Sorting. If you are working with a file on an application server, the data is fetched from the application server, and EWM displays it to you. 4. Make corrections if required.

For example, you are using a local CSV file A. After EWM has uploaded file A and is showing you the data, you notice that the formatting of the Excel file is incorrect. You correct the formatting and upload the file again. If you upload a file from an application server, you can make corrections directly in the LSMW and then upload the file again. 5. Choose

(Create Storage Bins).

EWM stores the data to the database. On the Successful Changes tab page, you can find all the storage bins that have been successfully created. On the Failed Changes tab page, you can find all the storage bins that EWM was unable to create. The column Message Line on this tab page also shows you the additional message text.

SAP Extended Warehouse Management (SAP EWM)

510

978

SAP Online Help

20.07.2007

Transfer Stock Data Use There are two ways to copy existing data: ●

By uploading a local file, such as a Comma-Separated-Values file (CSV file).

●

By uploading a file from an application server. In this case, Extended Warehouse Management (EWM) uses a connection to the Legacy System Migration Workbench [Extern] (LSMW). For more information about the LSMW, see SAP Library under mySAP ERP → SAP Oil & Gas → SAP Oil & Gas (ISOil Downstream) → Integration of SAP Oil & Gas with SAP CRM → F&A Pricing in Integration with SAP CRM → Legacy System Migration Workbench.

Notes If you are using a template for your product numbers, you have to specify the products in file you want to upload without this template.

Prerequisites Sie haben alle Lagerplätze definiert, für die Sie Bestandsdaten übernehmen möchten. In Customizing for EWM, choose Master Data.

Procedure ...

1. In the SAP Easy Access screen, choose Extended Warehouse Management → Interfaces → Stock Data Transfer. 2. Specify a Warehouse Number and Language, as the units of measure of languagedependent. The highest number of handling units per posting is set at 50 pieces. You can change this value. Set Do Not Post Data in ERP if required. 3. Group box Source a. Specify the location from which you want to upload the file: ■

From a local computer

■

From an application server

b. Enter the file name and choose Upload. EWM uploads the file and displays it to you. If you are working with a file on an application server, the data is fetched from the application server, and EWM displays it to you. Make corrections if required.

For example, you are using a local CSV file A. After EWM has uploaded file A and is showing you the data, you notice that the formatting of the CSV file is incorrect. You correct the formatting and upload the file again. If you upload a file from an application server, you can make corrections directly in the LSMW and then upload the file again. c. Choose the function

Execute Stock Data Transfer.

SAP Extended Warehouse Management (SAP EWM)

510

979

SAP Online Help

20.07.2007

EWM stores the data in the database, and shows you an error log if any errors occurred.

For more information, see the report documentation for report /SCWM/R_INITIALSTOCKUPLOAD.

SAP Extended Warehouse Management (SAP EWM)

510

980

SAP Online Help

20.07.2007

Integration of PPF and the Condition Technique Use Extended Warehouse Management (EWM) uses the Post Processing Framework [Extern] (PPF) to specify whether PPF is able to perform a PPF action (for example, printing a warehouse order) and which details (such as the printer) PPF should take into account when performing the PPF action. Within the PPF, EWM calls determination of the condition technique [Extern] in order to find the appropriate condition records [Extern] for performing a PPF action.

Prerequisites You have made the Customizing settings for PPF: ●

You have defined the PPF action definitions with the relevant processing types. In Customizing for the PPF action definition, you have defined the following data:

●

○

Processing Time

○

Scheduling

○

Determination Technique

○

Rule Type

○

Action Merging

You have specified the PPF conditions for the defined PPF action definitions.

You have made the Customizing settings for the condition technique. ●

You have defined condition tables [Extern]. In Customizing, you have defined your condition tables from the field catalog, which SAP delivers. You have selected fields from the field catalog as key fields. These fields represent the condition under which the condition technique finds the condition record. If a data record transferred by EWM matches your key fields, then condition technique finds the matching condition record.

In Customizing, you have defined condition types [Extern], and therefore the access sequence [Extern] to the condition tables to search. In Customizing, you have assigned your condition types to the relevant determination procedures [Extern]. The determination procedure specifies the conditions that you permit for determining data (such as, printer, form type) and specifies the sequence (access sequence) in which condition technique should consider them. ●

In Customizing, you have 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.

SAP Extended Warehouse Management (SAP EWM)

510

981

SAP Online Help

20.07.2007

Features The PPF is the framework for controlling scheduling and execution. PPF specifies the following in scheduling, using the condition technique: ●

Whether it should print a warehouse order or warehouse task, using the condition record that was found using the PPF action name

●

The SAP Smart Form that it should use to print a warehouse order or warehouse task

●

The printer that it should use to print a warehouse order or warehouse task

●

Spool parameters

●

Number of copies

For more information about the structure and Customizing for PPF, 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 (BC-SRV-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.

Activities PPF is always called from: ●

Warehouse order creation

●

Warehouse task confirmation

●

Transfer order confirmation

●

Warehouse task confirmation

●

The functions for creating, changing, and deleting handling units

You have no influence on these calls. However, from the warehouse management monitor, choose Print or Repeat Print to trigger the process manually from the warehouse order, warehouse task, or handling unit. ●

As soon as EWM has all the data for the warehouse order, it automatically calls PPF at the end of warehouse order creation.

●

EWM transfers the data (for example, which goods should be moved and to where) to PPF.

●

PPF triggers the determination that returns a PPF action as a result. SAP has defined a PPF action for each form type (for example, print warehouse order list, print warehouse order single form).

●

The PPF action is linked to a schedule condition (BAdI), which PPF uses to check whether the current action requested by EWM (for example, printing a warehouse order) can be performed.

SAP Extended Warehouse Management (SAP EWM)

510

982

SAP Online Help

20.07.2007

○

In the schedule condition, the PPF calls determination in the condition technique. Depending on your Customizing settings, the determination returns the relevant condition records to PPF.

○

If a logical condition is stored in the condition record, PPF checks this condition.

○

If the schedule condition applies, PPF performs the action at the time you have specified in Customizing for PPF. When performing the action, PPF calls the relevant BAdI, which in turn calls the function module for printing the SAP Smart Form.

○

If the schedule condition does not apply, PPF is not permitted to perform the action. PPF notifies EWM, which then displays a relevant message.

For more information about the structure and Customizing for 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 (BC-SRV-GBT).

Example ●

You define two condition records: ○

Condition record 001 for the warehouse process type 9999 for an internal stock transfer for activity area 0010 with the logical condition WFB01 (from source storage type 001A to destination storage type 001B)

○

Condition record 002 for the warehouse process type 9999 for an internal stock transfer for activity area 0010 with the logical condition WFB01 (from source storage type 001A to destination storage type 001C)

Condition record

Warehouse process type

Activity Area

Printer

Form

Spool

L PPF o action g i c a l c o n d i t i o n

001

9999

0010

PRINT01

FORM01

01

L WO_SIN C GLE 0 1

002

9999

0010

PRINT02

FORM02

02

L WO_SIN C

SAP Extended Warehouse Management (SAP EWM)

510

983

SAP Online Help

20.07.2007 0 GLE 2

003

9999

0010

PRINT01

FORM03

01

L WO_MU C TIPLE 0 1

004

9999

0010

PRINT02

FORM04

02

L WO_MU C TIPLE 0 2

●

EWM creates the warehouse order and transmits the following warehouse order data to the PPF. ○

Warehouse process type 9999

○

Activity area 0010

○

Source storage type 001A

○

Destination storage type 001B

●

PPF has created several PPF action definitions for printing warehouse order documents (for example, WO_SINGLE and WO_MULTIPLE).

●

For each PPF action definition, the PPF checks the schedule condition.

●

Using the data, in the schedule condition PPF triggers determination in the condition technique for the PPF action definition WO_SINGLE.

●

The determination finds the condition records 001, 002, 003, and 004, which correspond to the data transmitted.

●

The condition records 003 and 004 are not relevant for this PPF action definition. They are only evaluted for the PPF action definition WO_MULTIPLE.

●

After checking the logical condition (LK01 for condition record 001, and LK02 for condition record 002), condition record 001 is left over, since the logical condition in this condition record is fulfilled.

●

Since the system has found a valid entry, the PPF schedule condition is fulfilled. The system saves the results fields from the condition record (for example, printer, form) and uses these later during execution in the PPF method for printing. The system prints SAP Smart Form FORM01 on printer DRUCK01 using the spool parameters 01.

SAP Extended Warehouse Management (SAP EWM)

510

984

SAP Online Help

20.07.2007

Authorizations Use Extended Warehouse Management (EWM) uses the SAP authorization concept [Extern] to control the access to applications. For more information about the authorization function, see Users and Roles (BC-SEC-USR) [Extern] and Checking Authorizations [Extern].

Features The following table shows the authorization objects available in EWM. For more information, see the relevant system documentation. Authorization Object

Description

/SCWM/ACTI

Activity area

/SCWM/WST

Work center

/SCWM/TOHA

Process warehouse task

/SCWM/STLG

Stock at location type ‘warehouse number’

/SCWM/STBI

Stock at location type ‘storage bin'

/SCWM/STRS

Stock at location type ‘resource’

/SCTM/STTU

Stock at location type ‘transportation unit’

/SCWM/RFAD

Enhancement screen

/SCWM/CHG

Batch

/SCWM/TOCR

Create warehouse task

/SCWM/ESIC

Express delivery company

/SCWM/PIPR

Physical inventory

/SCWM/DLV

Warehouse Request

/SCWM/LG

Storage bin

/SCWM/SLOT

Slotting

/SCWM/RFLT

Logical transactions for RF

/SCWM/MO

Monitoring activities

/SCWM/QDOC

Inspection document

/SCWM/QFID

Inspection document - findings

/SCWM/QELM

Inspection document - element

/SCWM/QSUP

Inspection setup

/SCWM/QUEU

Queue

/SCWM/SFUN

Special functions

/SCWM/SLFU

Special functions per warehouse number

/SCWM/TR

Means of transportation

/SCWM/RSTY

Resource type

/SCWM/WAV2

Waves

SAP Extended Warehouse Management (SAP EWM)

510

985

SAP Online Help

20.07.2007

/SCWM/WAV1

Wave templates, condition records for wave template determination

/SCWM/VAS

VAS order processing

/SCWM/QLVL

Quality level

See also: Authorizations in Transportation Management [Seite 637]

SAP Extended Warehouse Management (SAP EWM)

510

986

SAP Online Help

20.07.2007

Roles for Extended Warehouse Management (EWM) Purpose The following topics contain information about the individual roles in Extended Warehouse Management (EWM): EWM: Warehouse Manager [Seite 988] EWM: Warehouse Expert [Seite 993] EWM: Warehouse Specialist for Goods Receipt [Seite 1001] EWM: Warehouse Specialist for Goods Issue [Seite 1004] EWM: Warehouse Specialist for Yard Management [Seite 1007] EWM: Warehouse Worker [Seite 1009] EWM: Physical Inventory Planner [Seite 1011] EWM: Physical Inventory Counter [Seite 1013] EWM: Displaying Warehouse Information [Seite 1014] EWM: ERP Integration [Seite 1015] EWM: Labor Planner [Seite 1016] EWM: Warehouse Analyst [Seite 1017] EWM: Warehouse Specialist for Labor Management [Seite 1018]

SAP Extended Warehouse Management (SAP EWM)

510

987

SAP Online Help

20.07.2007

EWM: Warehouse Manager Technical name: /SCWM/SUPERVISOR

Tasks You can use this role to execute all typical activities for a particular warehouse that you require as a warehouse manager in Extended Warehouse Management (EWM). These activities comprise shipping and receiving, and the complete overview of performing work operations. In addition, the system informs the warehouse manager if critical situations arise.

Activities in Extended Warehouse Management (EWM) You can display or edit data (such as create, change, or delete) in EWM on the following screens: Authorizations for Screens and Modes: Warehouse Manager Screen

Mode

Warehouse Management Monitor

Display

Goods Receipt Workload

Display

Monitor Correction Deliveries

Display

Warehouse Cockpit

Display

List of Hazardous Substances for Fire Department

Display

Maintain Inbound Delivery Notification

Edit

Maintain Inbound Delivery

Edit

GR Preparation - External Procurement

Edit

GR Preparation - Production

Edit

Physical Goods Receipt

Edit

Update Priority Points

Edit

Unload

Edit

Maintain Notification of Goods Receipt

Edit

Maintain Expected Goods Receipt

Edit

Generate or Delete Expected Goods Receipt

Edit

Maintain Outbound Delivery Request

Edit

Maintain Outbound Delivery Order

Edit

Maintain Outbound Delivery

Edit

Load

Edit

Pickup

Edit

Maintain Posting Change Request

Edit

Maintain Posting Change

Edit

Maintain Internal Stock Transfer

Edit

Maintain Conditions for Determining Wave Templates

Edit

SAP Extended Warehouse Management (SAP EWM)

510

988

SAP Online Help

20.07.2007

Maintain Waves

Edit

Putaway for Inbound Delivery

Edit

Stock Removal for Outbound Delivery Order

Edit

Transfer for Internal Stock Transfer

Edit

Transfer for Posting Change

Edit

Move Product

Edit

Move Handling Unit

Edit

Process Product Inspection Document

Edit

Process HU Inspection Document

Edit

Process Delivery Inspection Document

Edit

Rearrangement

Edit

Rearrangement (Background)

Edit

Analyze Stock Situation

Edit

Schedule Replenishment

Edit

Make Posting Change for Product

Edit

VAS in Goods Receipt Process

Edit

VAS in Goods Issue Process

Edit

VAS for Kit Creation on Stock

Edit

VAS for Reverse Kitting

Edit

VAS for Internal Warehouse Operations

Edit

Process and Display PPF Actions

Edit

Confirm Warehouse Task

Edit

Manually Assemble Warehouse Tasks

Edit

Deconsolidation in Goods Receipt

Edit

Quality Inspection and Count

Edit

Log On to RF Environment

Edit

Packing - General

Edit

Create Confirmation for VAS

Edit

Cancel Picking

Edit

Process Vehicle

Edit

Process Transportation Unit

Edit

Maintain Door Assignment

Edit

Load

Edit

Unload

Edit

Arrival at/Departure from Checkpoint

Edit

Create Warehouse Task in Yard

Edit

Maintain Shipment

Edit

Maintain Freight Document

Edit

SAP Extended Warehouse Management (SAP EWM)

510

989

SAP Online Help

20.07.2007

List of Changes

Display

Shipment Monitor

Display

Freight Monitor

Display

Display Application Log

Display

Consistency Check

Display

Create Physical Inventory Document

Edit

Print Physical Inventory Count Document

Edit

Process Physical Inventory Document

Edit

Enter Count Results

Edit

Create Physical Inventory Count in a List

Edit

Difference Analyzer

Edit

Create Physical Inventory Document (Cycle Counting)

Edit

Create Physical Inventory Document

Edit

Post Differences to ERP System

Edit

Check Product for Complete Count

Edit

Upload Storage Bins and Count Data

Edit

Download Storage Bins and Stock Data

Edit

Adjust Serial Numbers at Warehouse Number Level

Edit

Maintain Indirect Labor Task

Edit

Employee Performance Overview

View

Send Performance Document to HR

Edit

Assign User to Exception Code Profile

Edit

Link Between Packaging Material (TU) and Means of Transportation

Edit

Set Up Printer and Form Determination

Edit

Define Tailored Measurement Service

Edit

Define Calculated Measurement Service

Edit

Define Measurement Services in the Warehouse Cockpit

Edit

Start Measurement Services

Edit

Delete Measurement Service Results

Edit

Perform Update (Delivery)

Edit

Perform Update

Edit

Maintain BW Delta Queue

Edit

You can display or edit all settings for the following master data: Master Data

Mode

Maintain Supply Chain Unit

Edit

SAP Extended Warehouse Management (SAP EWM)

510

990

SAP Online Help

20.07.2007

Maintain Business Partner

Edit

Maintain Resource Group

Edit

Maintain Resource

Edit

Maintain Users

Edit

Create Processor

Edit

Change Processor

Edit

Maintain Business Partner

Edit

Create Storage Bin

Edit

Change Storage Bin

Edit

Mass Change to Storage Bins

Edit

Display Storage Bin

Display

Generate Storage Bins

Edit

Sort Storage Bins

Edit

Assign Source/Destination Storage Bin to Activity Area

Edit

Add User Status for Storage Bins

Edit

Maintain Fixed Storage Bin

Edit

Delete Fixed Storage Bin Assignments

Edit

Assign Fixed Storage Bins to Products

Edit

Maintain Product

Edit

Maintain Warehouse Product

Edit

Maintain Batches for Product

Edit

Display Generic Products

Display

Synchronize ERP/EWM Settings for Documentation Batches

Edit

Block Storage Type for Hazard Rating 1

Edit

Block Storage Type for Hazard Rating 2

Edit

Maintain Packaging Specification

Edit

Maintain Inspection Rule

Edit

Maintain Quality Level

Edit

Maintain Sample-Drawing Procedure

Edit

Define Master Data of Follow-Up Action

Edit

Default Owners of Transportation Units and Vehicles

Edit

Process Vehicle

Edit

Process Transportation Unit

Edit

Location

Edit

Transportation Lane

Edit

Delete Route

Edit

SAP Extended Warehouse Management (SAP EWM)

510

991

SAP Online Help

20.07.2007

Maintain Route

Edit

Delete Zones

Edit

Maintain Zones for Routes

Edit

Carrier Profile for the Routing Guide

Edit

Simulate Route Determination

Display

SAP Extended Warehouse Management (SAP EWM)

510

992

SAP Online Help

20.07.2007

EWM: Warehouse Expert Technical name: /SCWM/EXPERT

Tasks You can use this role to execute the typical activities that you require as a warehouse expert in Extended Warehouse Management (EWM). These activities comprise the configuration of the warehouse (layout) and the warehouse processes. The warehouse expert can also monitor warehouse processes and process exceptions.

Activities in Extended Warehouse Management (EWM) You can display or edit data (such as create, change, or delete) in EWM on the following screens: Authorizations for Screens and Modes: Warehouse Expert Screen

Mode

Warehouse Management Monitor

Display

Goods Receipt Workload

Display

Monitor Correction Deliveries

Display

Warehouse Cockpit

Display

Process Chart Template

Display

Inventory List of Hazardous Substances for Fire Department

Display

Maintain Inbound Delivery Notification

Edit

Maintain Inbound Delivery

Edit

GR Preparation - External Procurement

Edit

GR Preparation - Production

Edit

Physical Goods Receipt

Edit

Update Priority Points

Edit

Unload

Edit

Maintain Notification of Goods Receipt

Edit

Maintain Expected Goods Receipt

Edit

Generate or Delete Expected Goods Receipt

Edit

Maintain Outbound Delivery Request

Edit

Maintain Outbound Delivery Order

Edit

Maintain Outbound Delivery

Edit

Load

Edit

Pickup

Edit

Maintain Posting Change Request

Edit

Maintain Posting Change

Edit

Maintain Internal Stock Transfer

Edit

SAP Extended Warehouse Management (SAP EWM)

510

993

SAP Online Help

20.07.2007

Condition Records for PPF Schedule Condition

Edit

Maintain Conditions for Determining Wave Templates

Edit

Maintain Wave Templates

Edit

Maintain Waves

Edit

Putaway for Inbound Delivery

Edit

Stock Removal for Outbound Delivery Order

Edit

Transfer for Internal Stock Transfer

Edit

Transfer for Posting Change

Edit

Move Product

Edit

Move Handling Unit

Edit

Process Product Inspection Document

Edit

Process HU Inspection Document

Edit

Process Delivery Inspection Document

Edit

Rearrangement

Edit

Rearrangement (Background)

Edit

Analyze Stock Situation

Edit

Schedule Replenishment

Edit

Make Posting Change for Product

Edit

VAS in Goods Receipt Process

Edit

VAS in Goods Issue Process

Edit

VAS for Kit Creation on Stock

Edit

VAS for Reverse Kitting

Edit

VAS for Internal Warehouse Operations

Edit

Process and Display PPF Actions

Edit

Maintain Warehouse-Specific Printing Parameters

Edit

Create Logical Conditions for Printing (HUs)

Edit

Create Logical Conditions for Printing (Warehouse Orders)

Edit

Create Condition Records for Printing (HUs)

Edit

Create Condition Records for Printing (Warehouse Orders)

Edit

Create Condition Records for Printing (Physical Inventory)

Edit

Activate Application Log

Edit

Enhance Print Condition Tables

Edit

Confirm Warehouse Task

Edit

Manually Assemble Warehouse Tasks

Edit

Deconsolidation in Goods Receipt

Edit

SAP Extended Warehouse Management (SAP EWM)

510

994

SAP Online Help

20.07.2007

Quality Inspection and Count

Edit

Log On to RF Environment

Edit

Packing - General

Edit

Create Confirmation for VAS

Edit

Cancel Picking

Edit

Process Vehicle

Edit

Process Transportation Unit

Edit

Maintain Door Assignment

Edit

Load

Edit

Unload

Edit

Arrival at/Departure from Checkpoint

Edit

Create Warehouse Task in Yard

Edit

Maintain Shipment

Edit

Maintain Freight Document

Edit

List of Changes

Edit

Shipment Monitor

Display

Freight Monitor

Display

Display Application Log

Display

Consistency Check

Display

Create Physical Inventory Document

Edit

Process Physical Inventory Document

Edit

Enter Count Results

Edit

Create Physical Inventory Count in a List

Edit

Difference Analyzer

Edit

Determine and Set Prices from ERP

Edit

Create Physical Inventory Document

Edit

Create Physical Inventory Document (Cycle Counting)

Edit

Print Physical Inventory Count Document

Edit

Post Differences to ERP System

Edit

Check Product for Complete Count

Edit

Upload Storage Bins and Count Data

Edit

Download Storage Bins and Stock Data

Edit

Stock Comparison ERP

Edit

Adjust Serial Numbers at Warehouse Number Level

Edit

Maintain Indirect Labor Task

Edit

Planning and Simulation

Display

SAP Extended Warehouse Management (SAP EWM)

510

995

SAP Online Help

20.07.2007

Planning and Simulation Results

Display

Employee Performance Overview

Display

Send Performance Document to HR

Edit

Assign User to Exception Code Profile

Edit

Assignments: Warehouse Numbers/Business Partners

Edit

Assign Warehouse Number/Party Authorized to Customs ID

Edit

Activate Application Log

Edit

Maintain Goods Movement Bin Determination

Edit

Set Up Control Parameters for Warehouse Order Creation

Edit

Link Between Packaging Material (TU) and Means of Transportation

Edit

Staging Area and Door Determination (Inbound)

Edit

Staging Area and Door Determination (Outbound)

Edit

Access Sequence to Staging Area and Door Determination

Edit

Set Up Printer and Form Determination

Edit

Form Determination for Bills of Lading

Edit

Form Determination for Freight Documents

Edit

Printer Determination for Transportation Management

Edit

Define Printer Profile for Transportation Management

Edit

Settings for the Travel Distance Calculation

Edit

Generate Network

Edit

Assign User to Tolerance Group for Difference Analyzer

Edit

Assign User to Tolerance Group for Recount/Clearing

Edit

Tailored Measurement Service with Wizard

Edit

Calculated Measurement Service with Wizard

Edit

Define Tailored Measurement Service

Edit

Define Calculated Measurement Service

Edit

Define Measurement Services in the Warehouse Cockpit

Edit

Configure Measurement Services in the Warehouse Cockpit

Edit

Upload Engineered Labor Standards

Edit

Condition Editor

Edit

SAP Extended Warehouse Management (SAP EWM)

510

996

SAP Online Help

20.07.2007

Formula Editor

Edit

Determine RFC Connection for SAP AII Communication

Edit

Disallow RFID Goods Movements

Edit

Encode RFID Transponder for Resource

Edit

Enhance Print Condition Tables for RFID Printer

Edit

Stock Data Transfer

Edit

Initial Data Transfer of Packaging Specifications

Edit

Invoice Before Goods Issue

Edit

Load Storage Bins

Edit

Load Storage Bin Sorting

Edit

Administration of Account Assignment Data

Edit

Delete Setup Table

Edit

Setup of Delivery Items

Edit

Setup of Storage Bins

Edit

Setup of Warehouse Tasks

Edit

Setup of Warehouse Orders

Edit

Setup of Value-Added Services

Edit

Display Setup Table (Extractor Checker)

Display

Define Tailored Measurement Service

Edit

Define Calculated Measurement Service

Edit

Start Measurement Services

Edit

Delete Measurement Service Results

Edit

Perform Update (Delivery)

Edit

Perform Update

Edit

Maintain BW Delta Queue

Edit

You can display or edit all settings for the following master data: Master Data

Mode

Maintain Supply Chain Unit

Edit

Maintain Business Partner

Edit

Maintain Presentation Devices

Edit

Maintain Consolidation Group

Edit

Assign Storage Bins for VAS Consumption Posting

Edit

Administration of Characteristics

Display

Administration of Classes

Display

Maintain Resource Group

Edit

SAP Extended Warehouse Management (SAP EWM)

510

997

SAP Online Help

20.07.2007

Maintain Queue Sequence for Resource Group

Edit

Maintain Resource

Edit

Maintain Execution Priorities

Edit

Maintain Users

Edit

Create Processor

Edit

Change Processor

Edit

Maintain Business Partner

Edit

Activate Plan Values

Edit

Slot Products for Warehouse

Edit

Simulate Slotting

Edit

Condition Maintenance for Slotting

Edit

Create Storage Bin

Edit

Change Storage Bin

Edit

Mass Change to Storage Bins

Edit

Display Storage Bin

Display

Generate Storage Bins

Edit

Sort Storage Bins

Edit

Assign Source/Destination Storage Bin to Activity Area

Edit

Add User Status for Storage Bins

Edit

Maintain Fixed Storage Bin

Edit

Delete Fixed Storage Bin Assignments

Edit

Assign Fixed Storage Bins to Products

Edit

Print Storage Bin Label

Edit

Print Fixed Storage Bin Label

Edit

Maintain Verification Field

Edit

Load Storage Bins

Edit

Load Storage Bin Sorting

Edit

Maintain Product

Edit

Maintain Warehouse Product

Edit

Maintain Batches for Product

Edit

Display Generic Products

Display

Synchronize ERP/EWM Settings for Documentation Batches

Edit

Block Storage Type for Hazard Rating 1

Edit

Block Storage Type for Hazard Rating 2

Edit

Define Master Data Attributes

Edit

Determine Work Center in Goods Issue

Edit

SAP Extended Warehouse Management (SAP EWM)

510

998

SAP Online Help

20.07.2007

Printer Control

Edit

Define Scales

Edit

Maintain Packaging Specification

Edit

Maintain Packaging Work Step

Edit

Maintain Level Element Group

Edit

Condition Maintenance

Edit

Define Logical Conditions for Packaging Specifications

Edit

Define Master Data for Packaging Specifications

Edit

Initial Data Transfer of Packaging Specifications

Edit

Maintain Inspection Rule

Edit

Maintain Quality Level

Edit

Maintain Sample-Drawing Procedure

Edit

Define Master Data of Follow-Up Action

Edit

Maintain Communication Points

Edit

Maintain Conveyor Segments

Edit

Maintain Conveyor Segment Groups

Edit

Maintain Programmable Logic Controller

Edit

Maintain Communication Channel

Edit

Generate Application Data

Edit

Delete Telegram Log

Edit

Generate PLC Objects from EWM Objects

Edit

Map EWM Objects to PLC Objects

Edit

Maintain MFS Resource

Edit

Default Owners of Transportation Units and Vehicles

Edit

Process Vehicle

Edit

Process Transportation Unit

Edit

Assign Door to Storage Bin and Supply Chain Unit

Edit

Create Storage Bin

Edit

Assign Warehouse Door to Yard Bin

Edit

Assign Checkpoint to Yard Bin and Supply Chain Unit

Edit

Define General Transportation Cost Profile

Edit

General Settings for Route Determination

Edit

Assign Calendar to Supply Chain Unit

Edit

Location

Edit

SAP Extended Warehouse Management (SAP EWM)

510

999

SAP Online Help

20.07.2007

Transportation Lane

Edit

Delete Route

Edit

Maintain Route

Edit

Delete Zones

Edit

Maintain Zones for Routes

Edit

Carrier Profile for the Routing Guide

Edit

Simulate Route Determination

Display

SAP Extended Warehouse Management (SAP EWM)

510

1000

SAP Online Help

20.07.2007

EWM: Warehouse Specialist for Goods Receipt Technical name: /SCWM/INBD_SPECIALIST

Tasks You can use this role to execute the typical activities that you require as a warehouse specialist for goods receipt in Extended Warehouse Management (EWM).

Activities in Extended Warehouse Management (EWM) You can display or edit data (such as create, change, or delete) in EWM on the following screens: Authorizations for Screens and Modes: Warehouse Specialist for Goods Receipt Screen

Mode

Warehouse Management Monitor

Display

Goods Receipt Workload

Display

Warehouse Cockpit

Display

List of Hazardous Substances for Fire Department

Display

Maintain Inbound Delivery Notification

Edit

Maintain Inbound Delivery

Edit

GR Preparation - External Procurement

Edit

GR Preparation - Production

Edit

Physical Goods Receipt

Edit

Update Priority Points

Edit

Unload

Edit

Maintain Notification of Goods Receipt

Edit

Maintain Expected Goods Receipt

Edit

Generate or Delete Expected Goods Receipt

Edit

Maintain Posting Change Request

Edit

Maintain Posting Change

Edit

Maintain Internal Stock Transfer

Edit

Putaway for Inbound Delivery

Edit

Transfer for Internal Stock Transfer

Edit

Transfer for Posting Change

Edit

Move Product

Edit

Move Handling Unit

Edit

Process Product Inspection Document

Edit

Process HU Inspection Document

Edit

Process Delivery Inspection Document

Edit

Rearrangement

Edit

SAP Extended Warehouse Management (SAP EWM)

510

1001

SAP Online Help

20.07.2007

Rearrangement (Background)

Edit

Analyze Stock Situation

Edit

Make Posting Change for Product

Edit

VAS in Goods Receipt Process

Edit

VAS for Kit Creation on Stock

Edit

VAS for Reverse Kitting

Edit

VAS for Internal Warehouse Operations

Edit

Process and Display PPF Actions

Edit

Confirm Warehouse Task

Edit

Deconsolidation in Goods Receipt

Edit

Quality Inspection and Count

Edit

Log On to RF Environment

Edit

Packing - General

Edit

Create Confirmation for VAS

Edit

Process Vehicle

Edit

Process Transportation Unit

Edit

Maintain Door Assignment

Edit

Unload

Edit

Maintain Shipment

Edit

Maintain Freight Document

Edit

List of Changes

Display

Shipment Monitor

Display

Freight Monitor

Display

Display Application Log

Display

Consistency Check

Display

Maintain Indirect Labor Task

Edit

Assign User to Exception Code Profile

Edit

Perform Update (Delivery)

Edit

Perform Update

Edit

Maintain BW Delta Queue

Edit

You can display or edit all settings for the following master data: Master Data

Mode

Maintain Supply Chain Unit

Edit

Maintain Business Partner

Edit

Maintain Resource

Edit

Maintain Users

Edit

Change Storage Bin

Edit

Display Storage Bin

Display

SAP Extended Warehouse Management (SAP EWM)

510

1002

SAP Online Help

20.07.2007

Sort Storage Bins

Edit

Assign Source/Destination Storage Bin to Activity Area

Edit

Add User Status for Storage Bins

Edit

Maintain Fixed Storage Bin

Edit

Delete Fixed Storage Bin Assignments

Edit

Assign Fixed Storage Bins to Products

Edit

Print Storage Bin Label

Edit

Print Fixed Storage Bin Label

Edit

Maintain Product

Edit

Maintain Warehouse Product

Edit

Maintain Batches for Product

Edit

Display Generic Products

Display

Synchronize ERP/EWM Settings for Documentation Batches

Edit

Maintain Packaging Specification

Edit

Maintain Inspection Rule

Edit

Maintain Quality Level

Edit

Maintain Sample-Drawing Procedure

Edit

Define Master Data of Follow-Up Action

Edit

Default Owners of Transportation Units and Vehicles

Edit

Process Vehicle

Edit

Process Transportation Unit

Edit

Location

Edit

Transportation Lane

Edit

Delete Routes

Edit

Maintain Route

Edit

Delete Zones

Edit

Maintain Zones for Routes

Edit

Carrier Profile for the Routing Guide

Edit

Simulate Route Determination

Display

SAP Extended Warehouse Management (SAP EWM)

510

1003

SAP Online Help

20.07.2007

EWM: Warehouse Specialist for Goods Issue Technical name: /SCWM/OUTBD_SPECIALIST

Tasks You can use this role to execute the typical activities that you require as a warehouse specialist for goods issue in Extended Warehouse Management (EWM).

Activities in Extended Warehouse Management (EWM) You can display or edit data (such as create, change, or delete) in EWM on the following screens: Authorizations for Screens and Modes: Warehouse Specialist for Goods Issue Screen

Mode

Warehouse Management Monitor

Display

Monitor Correction Deliveries

Display

Warehouse Cockpit

Display

List of Hazardous Substances for Fire Department

Display

Maintain Outbound Delivery Request

Edit

Maintain Outbound Delivery Order

Edit

Maintain Outbound Delivery

Edit

Load

Edit

Pickup

Edit

Maintain Posting Change Request

Edit

Maintain Posting Change

Edit

Maintain Internal Stock Transfer

Edit

Maintain Waves

Edit

Stock Removal for Outbound Delivery Order

Edit

Transfer for Internal Stock Transfer

Edit

Transfer for Posting Change

Edit

Move Product

Edit

Move Handling Unit

Edit

Rearrangement

Edit

Rearrangement (Background)

Edit

Analyze Stock Situation

Edit

Schedule Replenishment

Edit

Make Posting Change for Product

Edit

VAS in Goods Issue Process

Edit

VAS for Kit Creation on Stock

Edit

VAS for Reverse Kitting

Edit

SAP Extended Warehouse Management (SAP EWM)

510

1004

SAP Online Help

20.07.2007

VAS for Internal Warehouse Operations

Edit

Process and Display PPF Actions

Edit

Confirm Warehouse Task

Edit

Log On to RF Environment

Edit

Packing - General

Edit

Create Confirmation for VAS

Edit

Cancel Picking

Edit

Process Vehicle

Edit

Process Transportation Unit

Edit

Maintain Door Assignment

Edit

Load

Edit

Maintain Shipment

Edit

Maintain Freight Document

Edit

List of Changes

Display

Shipment Monitor

Display

Freight Monitor

Display

Display Application Log

Display

Consistency Check

Display

Maintain Indirect Labor Task

Edit

Assign User to Exception Code Profile

Edit

Link Between Packaging Material (TU) and Means of Transportation

Edit

Set Up Printer and Form Determination

Edit

Perform Update (Delivery)

Edit

Perform Update

Edit

Maintain BW Delta Queue

Edit

You can display or edit all settings for the following master data: Master Data

Mode

Maintain Supply Chain Unit

Edit

Maintain Business Partner

Edit

Maintain Consolidation Group

Edit

Maintain Resource

Edit

Maintain Users

Edit

Change Storage Bin

Edit

Display Storage Bin

Display

Sort Storage Bins

Edit

Assign Source/Destination Storage Bin to Activity Area

Edit

SAP Extended Warehouse Management (SAP EWM)

510

1005

SAP Online Help

20.07.2007

Add User Status for Storage Bins

Edit

Maintain Fixed Storage Bin

Edit

Delete Fixed Storage Bin Assignments

Edit

Assign Fixed Storage Bins to Products

Edit

Print Storage Bin Label

Edit

Print Fixed Storage Bin Label

Edit

Maintain Product

Edit

Maintain Warehouse Product

Edit

Maintain Batches for Product

Edit

Maintain Packaging Specification

Edit

Display Generic Products

Display

Synchronize ERP/EWM Settings for Documentation Batches

Edit

Default Owners of Transportation Units and Vehicles

Edit

Process Vehicle

Edit

Process Transportation Unit

Edit

Location

Edit

Transportation Lane

Edit

Delete Routes

Edit

Maintain Route

Edit

Delete Zones

Edit

Maintain Zones for Routes

Edit

Carrier Profile for the Routing Guide

Edit

Simulate Route Determination

Display

SAP Extended Warehouse Management (SAP EWM)

510

1006

SAP Online Help

20.07.2007

EWM: Warehouse Specialist for Yard Management Technical name: /SCWM/YARD_SPECIALIST

Tasks You can use this role to execute the typical activities that you require as a warehouse specialist for yard management in Extended Warehouse Management (EWM).

Activities in Extended Warehouse Management (EWM) You can display or edit data (such as create, change, or delete) in EWM on the following screens: Authorizations for Screens and Modes: Warehouse Specialist for Yard Management Screen

Mode

Warehouse Management Monitor

Display

Warehouse Cockpit

Display

List of Hazardous Substances for Fire Department

Display

Maintain Inbound Delivery Notification

Edit

Maintain Inbound Delivery

Edit

GR Preparation - External Procurement

Edit

GR Preparation - Production

Edit

Physical Goods Receipt

Edit

Update Priority Points

Edit

Unload

Edit

Maintain Notification of Goods Receipt

Edit

Maintain Expected Goods Receipt

Edit

Generate or Delete Expected Goods Receipt

Edit

Maintain Outbound Delivery Request

Edit

Maintain Outbound Delivery Order

Edit

Maintain Outbound Delivery

Edit

Load

Edit

Maintain Internal Stock Transfer

Edit

Process and Display PPF Actions

Edit

Confirm Warehouse Task

Edit

Log On to RF Environment

Edit

Packing - General

Edit

Process Vehicle

Edit

Process Transportation Unit

Edit

Maintain Door Assignment

Edit

Load

Edit

SAP Extended Warehouse Management (SAP EWM)

510

1007

SAP Online Help

20.07.2007

Unload

Edit

Arrival at/Departure from Checkpoint

Edit

Create Warehouse Task in Yard

Edit

Maintain Shipment

Edit

Maintain Freight Document

Edit

Display List of Changes

Display

Shipment Monitor

Display

Freight Monitor

Display

Display Application Log

Display

Consistency Check

Display

Maintain Indirect Labor Task

Edit

Assign User to Exception Code Profile

Edit

You can display or edit all settings for the following master data: Master Data

Mode

Maintain Resource

Edit

Maintain Users

Edit

Create Storage Bin

Edit

Change Storage Bin

Edit

Display Storage Bin

Display

Default Owners of Transportation Units and Vehicles

Edit

Process Vehicle

Edit

Process Transportation Unit

Edit

Location

Edit

Transportation Lane

Edit

Delete Routes

Edit

Maintain Route

Edit

Delete Zones

Edit

Maintain Zones for Routes

Edit

Carrier Profile for the Routing Guide

Edit

Simulate Route Determination

Display

SAP Extended Warehouse Management (SAP EWM)

510

1008

SAP Online Help

20.07.2007

EWM: Warehouse Worker Technical name: /SCWM/WORKER

Tasks You can use this role to execute the typical activities that you require as a warehouse worker in Extended Warehouse Management (EWM). These activities comprise confirming warehouse tasks, physical inventory counting, and warehouse information.

Activities in Extended Warehouse Management (EWM) You can display or edit data (such as create, change, or delete) in EWM on the following screens: Authorizations for Screens and Modes: Warehouse Worker Screen

Mode

Warehouse Management Monitor

Display

Maintain Inbound Delivery

Edit

Unload

Edit

Maintain Outbound Delivery Order

Edit

Maintain Outbound Delivery

Edit

Load

Edit

Maintain Posting Change

Edit

Maintain Internal Stock Transfer

Edit

Move Product

Edit

Move Handling Unit

Edit

Process and Display PPF Actions

Edit

Confirm Warehouse Task

Edit

Deconsolidation in Goods Receipt

Edit

Quality Inspection and Count

Edit

Log On to RF Environment

Edit

Packing - General

Edit

Create Confirmation for VAS

Edit

Maintain Door Assignment

Edit

Load

Edit

Unload

Edit

List of Changes

Display

Shipment Monitor

Display

Freight Monitor

Display

Consistency Check

Display

Process Physical Inventory Document

Edit

Enter Count Results

Edit

SAP Extended Warehouse Management (SAP EWM)

510

1009

SAP Online Help

20.07.2007

Create Physical Inventory Count in a List

Edit

Maintain Indirect Labor Task

Edit

You can display or edit all settings for the following master data: Master Data

Mode

Change Storage Bin

Edit

Display Storage Bin

Display

Print Storage Bin Label

Edit

Print Fixed Storage Bin Label

Edit

Maintain Product

Edit

Maintain Warehouse Product

Edit

Maintain Batches for Product

Edit

Display Generic Products

Display

Synchronize ERP/EWM Settings for Documentation Batches

Edit

Maintain Packaging Specification

Edit

SAP Extended Warehouse Management (SAP EWM)

510

1010

SAP Online Help

20.07.2007

EWM: Physical Inventory Planner Technical name: /SCWM/INVENTORY_PLANNER

Tasks You can use this role to execute the typical activities that you require as a physical inventory planner in Extended Warehouse Management (EWM).

Activities in Extended Warehouse Management (EWM) You can display or edit data (such as create, change, or delete) in EWM on the following screens: Authorizations for Screens and Modes: Physical Inventory Planner Screen

Mode

Warehouse Management Monitor

Display

Warehouse Cockpit

Display

Monitor Correction Deliveries

Display

List of Hazardous Substances for Fire Department

Display

Process and Display PPF Actions

Edit

Log On to RF Environment

Edit

Packing - General

Edit

Create Physical Inventory Document

Edit

Process Physical Inventory Document

Edit

Enter Count Results

Edit

Create Physical Inventory Count in a List

Edit

Difference Analyzer

Edit

Maintain Indirect Labor Task

Edit

Create Physical Inventory Document (Cycle Counting)

Edit

Create Physical Inventory Document

Edit

Print Physical Inventory Count Document

Edit

Post Differences to ERP System

Edit

Check Product for Complete Count

Edit

Upload Storage Bins and Count Data

Edit

Download Storage Bins and Stock Data

Edit

Adjust Serial Numbers at Warehouse Number Level

Edit

You can display or edit all settings for the following master data: Master Data

Mode

Maintain Resource

Edit

SAP Extended Warehouse Management (SAP EWM)

510

1011

SAP Online Help

20.07.2007

Maintain Users

Edit

Change Storage Bin

Edit

Display Storage Bin

Display

Sort Storage Bins

Edit

Assign Source/Destination Storage Bin to Activity Area

Edit

Print Storage Bin Label

Edit

Add User Status for Storage Bins

Edit

Print Fixed Storage Bin Label

Edit

Maintain Product

Edit

Maintain Warehouse Product

Edit

Maintain Batches for Product

Display

Display Generic Products

Display

Synchronize ERP/EWM Settings for Documentation Batches

Edit

SAP Extended Warehouse Management (SAP EWM)

510

1012

SAP Online Help

20.07.2007

EWM: Physical Inventory Counter Technical name: /SCWM/COUNTER

Tasks You can use this role to execute the typical activities that you require as a physical inventory counter in Extended Warehouse Management (EWM).

Activities in Extended Warehouse Management (EWM) You can display or edit data (such as create, change, or delete) in EWM on the following screens: Authorizations for Screens and Modes: Physical Inventory Counter Screen

Mode

Log On to RF Environment

Edit

Packing - General

Edit

Quality Inspection and Count

Edit

Enter Count Results

Edit

Enter Physical Inventory Count in a List

Edit

Maintain Indirect Labor Task

Edit

You can display or edit all settings for the following master data: Master Data

Mode

Display Storage Bin

Display

SAP Extended Warehouse Management (SAP EWM)

510

1013

SAP Online Help

20.07.2007

EWM: Displaying Warehouse Information Technical name: /SCWM/INFORMATION

Tasks You can use this role to display warehouse information such as stock or statuses in Extended Warehouse Management (EWM).

Activities in Extended Warehouse Management (EWM) You can display data in EWM on the following screens: Authorizations for Screens and Modes: Displaying Warehouse Information Screen

Mode

Warehouse Management Monitor

Display

Maintain Inbound Delivery

Display

Maintain Outbound Delivery Order

Display

Maintain Outbound Delivery

Display

Shipment Monitor

Display

Freight Monitor

Display

SAP Extended Warehouse Management (SAP EWM)

510

1014

SAP Online Help

20.07.2007

EWM: ERP Integration Technical name: /SCWM/ERP_EWM_INTEGRATION

Tasks You need at least one RFC connection for the integration of SAP EWM and SAP ERP. To protect the RFC connection against misuse in the target system, give the background owner in EWM the minimum authorizations only. This role contains the authorization profile required for this RFC user (ALEREMOTE). Assign this role to the RFC user that you use for the integration of SAP EWM and SAP ERP.

SAP Extended Warehouse Management (SAP EWM)

510

1015

SAP Online Help

20.07.2007

EWM Labor Planner Technical name: /SCWM/LM_PLANNER

Tasks You can use this role to execute the typical activities that you require as a labor planner in Extended Warehouse Management (EWM).

Activities in Labor Management (LM) You can edit LM data (such as create, change, or delete) on the following screens: Authorizations for Screens and Modes: Labor Planner Screen

Modes

Planning and Simulation

Edit

Load Planning and Simulation Results

Edit

Engineered Labor Standards

Edit

Tailored Measurement Service with Wizard

Edit

Calculated Measurement Service with Wizard

Edit

Define Tailored Measurement Service

Edit

Define Calculated Measurement Service

Edit

Define Measurement Services in the Warehouse Cockpit

Edit

Configure Measurement Services in the Warehouse Cockpit

Edit

Start Measurement Services

Edit

Delete Measurement Service Results

Edit

Condition Editor

Edit

Formula Editor

Edit

SAP Extended Warehouse Management (SAP EWM)

510

1016

SAP Online Help

20.07.2007

EWM: Warehouse Analyst Technical name: SCWM/ANALYST

Tasks You can use this role to execute the typical activities that you require as a warehouse analyst in Extended Warehouse Management (EWM).

Activities in Extended Warehouse Management (EWM) You can edit EWM data (such as create, change, or delete) on the following screens: Authorizations for Screens and Modes: Warehouse Analyst Screen

Mode

Tailored Measurement Service with Wizard

Edit

Calculated Measurement Service with Wizard

Edit

Define Tailored Measurement Service

Edit

Define Calculated Measurement Service

Edit

Define Measurement Services in the Warehouse Cockpit

Edit

Configure Measurement Services in the Warehouse Cockpit

Edit

Start Measurement Services

Edit

Delete Measurement Service Results

Edit

Condition Editor

Edit

Formula Editor

Edit

SAP Extended Warehouse Management (SAP EWM)

510

1017

SAP Online Help

20.07.2007

EWM: Warehouse Specialist for Labor Management Technical name: /SCWM/LM_SPECIALIST

Tasks You can use this role to execute the typical activities that you require as a warehouse specialist for Labor Management in Extended Warehouse Management (EWM).

Activities in Labor Management (LM) You can display or edit LM data (such as create, change, or delete) on the following screens: Authorizations for Screens and Modes: Warehouse Specialist for Labor Management Screen

Mode

Maintain Indirect Labor Task

Edit

Employee Performance Overview

Edit

Send Performance Document to HR

Edit

Create Processor

Edit

Edit Processor

Edit

Maintain Business Partner

Edit

Executed Workload

Display

SAP Extended Warehouse Management (SAP EWM)

510

1018

SAP Online Help

20.07.2007

Data Archiving Purpose With the increased use of a productive business application, the volume of master data and transaction data in the system database can grow rapidly, which can, in turn, lead to reduced performance and increased costs. SAP data archiving, an SAP NetWeaver function, enables you to control your data volume on a long-term basis by relocating data that is no longer needed in the current business processes to archive files. Here, the data remains available for read-only access. The data archiving solution in the application-specific areas is based on the SAP standard solution for data archiving, which so far has been used in SAP ERP solutions, for example. Before you start archiving, we recommend that you familiarize yourself with the fundamentals of SAP data archiving. For more information about data archiving, see Introduction to Data Archiving [Seite 1020].

Overview of Archiving Documentation To enable you to access the information that you need for your archiving more quickly, the documentation is structured as follows: ●

The introduction to data archiving explains the basics of SAP data archiving and describes the relevant processes and procedures. This is indispensable reading for understanding data archiving.

●

The documentation for data archiving in the application-specific area contains specific information about using the relevant archiving objects to archive business objects.

SAP Extended Warehouse Management (SAP EWM)

510

1019

SAP Online Help

20.07.2007

Introduction to Data Archiving (CA-ARC) Data Archiving – a service provided by SAP NetWeaver – removes mass data that the system no longer needs online, but which must still be accessible at a later date if required, from the database. The following graphic illustrates the archiving process: Archiving objects are used to write documents to archive files, which can be stored on other media.

Online

Online/Nearline

Offline

Display

Archive Access

Database

Database Tables

Application Data

File System

Archive Files

Write and Delete

Storage System

Archive Files

Store

Data in the database can only be archived using archiving objects, which describe the data structure and context.

Financial Accounting documents are archived using the archiving object FI_DOCUMNT. It includes the document header, company code-dependent postings, change documents, SAPscript texts, and other elements. In addition to the aforementioned technology SAP also offers XML-based archiving, as of SAP Web Application Server 6.40. With this new procedure XML archiving objects are used to write data in the form of resources either to a file system or directly to a WebDAV system, which takes on the role of the storage system shown in the figure above.

Integration For the majority of the archiving objects the SAP Data Archiving concept is based on the Archive Development Kit (ADK). As of SAP Web AS 6.40 SAP offers an additional technology especially designed for XML-based archiving. This new technology comprises the XML Data Archiving Service (XML DAS) and the XML DAS Connector. Both ADK-based and XMLbased archiving are carried out with the help of Archive Administration, transaction SARA. For some applications it is possible to start archiving directly from the application menu. In these cases the application-specific parameters, such as the archiving object or the archiving program appear as default values. Archiving objects for each application component are predefined in the system. Their structures are described in the application-specific sections.

Features The archiving procedure is divided into three main steps: ●

Creation of archive files

SAP Extended Warehouse Management (SAP EWM)

510

1020

SAP Online Help

20.07.2007

In the write phase the data to be archived is written sequentially into newly created archive files. ●

Delete from the database The delete program reads the data from the archive files and then deletes it from the database.

●

Storage of archive files The newly created archive files can then be moved to a storage system or copied to a tape. The removal to an external storage system can be triggered manually or automatically. It is also possible to store the data before the delete phase. In XML-based archiving this phase does not exist as a separate step. The data can be written directly to a WebDAV system.

The archiving programs are generally scheduled in the background. However, they can also run in online mode. The following documentation describes ADK-based archiving. It is important that you understand the basic archiving concepts described in this documentation before you begin with XML-based archiving. The differences between the two technologies and processes are described under XML-based Archiving [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

1021

SAP Online Help

20.07.2007

Archiving in Extended Warehouse Management (SCM-EWM) Purpose You can archive the following data in Extended Warehouse Management (EWM): ●

Archiving in Delivery Processing [Seite 1024]

Document Category

Archiving Object

Internal Warehouse Requests (Inbound Delivery)

DLV_INB [Seite 1026]

Internal Warehouse Requests

DLV_OUT [Seite 1028]

Warehouse Requests from External Systems

DLV_REQ [Seite 1030]

●

Archiving in Quality Management [Seite 1032]

Document Category

Archiving Object

QIE Inspection Documents

QIE_INSP [Seite 1033]

●

Archiving in Shipping and Receiving [Seite 1044]

Document Category

Archiving Object

Door Activities

WME_DOOR [Seite 1052]

Vehicle Activities

WME_VEH [Seite 1045]

TU Activities

WME_TU [Seite 1048]

●

Archiving for Value-Added Services [Seite 1059]

Document Category

Archiving Object

Value-Added Service Orders (VAS Orders)

WME_VAS [Seite 1060]

●

Archiving in Transportation Management [Seite 1055]

Document Category

Archiving Object

Shipments

TM_SHP [Seite 1056]

Freight Documents

TM_FRD [Seite 1058]

●

Archiving in Wave Management [Seite 1062]

Document Category

Archiving Object

Waves

WME_WAVE [Seite 1063]

●

Archiving in Warehouse Order Processing [Seite 1065]

Document Category

Archiving Object

Telegram Flows

WME_MFS [Seite 1066]

Relevant Resource Data

WME_RSRC [Seite 1068]

Warehouse Tasks

WME_TO [Seite 1070]

Warehouse Orders

WME_WO [Seite 1072]

●

Archiving in Labor Management (LM) [Seite 1074]

SAP Extended Warehouse Management (SAP EWM)

510

1022

SAP Online Help

20.07.2007

Document Category

Archiving Object

Performance Documents

WME_EPD [Seite 1075]

Executed Workload

WME_EWL [Seite 1077]

Indirect Labor Tasks

WME_ILT [Seite 1078]

See also: Archiving Object [Extern]

SAP Extended Warehouse Management (SAP EWM)

510

1023

SAP Online Help

20.07.2007

Archiving in Delivery Processing (SCM-ECT-DLP) Use You can use archiving to remove data records for warehouse requests [Extern] that are no longer required in the system from the database.

Integration Delivery Processing uses the central data archiving. For more information about this service, see Introduction to Data Archiving [Seite 1020] (CA-ARC).

Prerequisites The documents to be archived must have the status Completed and the retention period [Extern] of the documents must have expired.

Features Report /SCDL/BO_ARCHIVE You use this report for all documents whose expiry date has been reached to change their status from Completed to To Be Archived. You define the retention period of the documents via the document type. In the selection screen of the report, you can select the documents to be archived via the selection criteria document type and document identification. You can also define whether the detailed log is to be displayed on the user interface after running the report or whether it is to be saved. You can also simulate a program run. You can schedule this report to run in the background or you can start it manually.

If you want to archive inbound delivery notifications or outbound delivery requests, you must first execute the report for all relevant follow-on documents (inbound deliveries, outbound delivery orders, and outbound deliveries).

Archiving Objects from Delivery Processing Each document category is assigned to an archiving object [Extern] that contains exact information about which data the system is to archive and how. Document Categories and their Archiving Objects for Delivery Processing Document Category

Archiving Object

Inbound Delivery Notification

DLV_REQ [Seite 1030]

Inbound Delivery

DLV_INB [Seite 1026]

Outbound Delivery Request

DLV_REQ [Seite 1030]

Outbound Delivery Order

DLV_OUT [Seite 1028]

Outbound Delivery

DLV_OUT [Seite 1028]

Posting Change

DLV_OUT [Seite 1028]

Posting Change Request

DLV_REQ [Seite 1030]

Stock Transfer

DLV_OUT [Seite 1028]

The archiving objects provide a series of actions that you can use in the archive administration (transaction SARA) for the data records in Delivery Processing.

SAP Extended Warehouse Management (SAP EWM)

510

1024

SAP Online Help

20.07.2007

Activities Preparing Documents for Archiving Before archiving, you have to change the status of all the documents to be archived whose expiry date has been exceeded from Completed to To Be Archived. ...

1. Choose transaction /SCDL/BO_ARCHIVE. 2. In the selection screen, enter the document type and the document identification of the documents that you want to archive. 3. Choose

Execute.

You can also schedule this report to run in the background.

Archiving For more information about the procedure for writing, deleting, and reading data records, see Archiving Procedure [Extern] in data archiving (CA-ARC).

SAP Extended Warehouse Management (SAP EWM)

510

1025

SAP Online Help

20.07.2007

Archiving Internal Warehouse Requests (Inb. Del.) (SCM-ECT-DLP) Definition Archiving object DLV_INB for archiving and deleting inbound deliveries [Seite 88].

Structure The following programs are available for DLV_INB: Program

Function

/SCDL/DLV_INB_ARCH_WRITE

Write

/SCDL/DLV_INB_ARCH_DELETE

Delete

/SCDL/DLV_INB_ACRH_READ

Read

Write The write program reads the data records of the documents to be archived from the database and records them in an archive file. In the selection screen of the write program, you can select the documents to be archived using the selection criteria in Deliveries and Restrictions. In the process control, you can determine whether you want the write report to start in either test or production mode. If you have activated the automatic start of the deletion program in archiving-object-specific Customizing, you can also define here that delivery processing starts the deletion program of the archiving object with the test mode variant saved in archiving-object-specific Customizing. When delivery processing executes the write program, it records a log containing information about the processed data records. In the selection screen of the write program, you can define that a detailed log is to be displayed in delivery processing. In addition to the information contained in the log, this contains all processed objects including the associated messages. Prerequisites for Writing Data Records The documents to be archived must have the status To Be Archived (see Archiving in Delivery Processing [Seite 1024]).

Delete The delete program deletes the data records from the database that were previously archived with the write program. In the selection screen of the delete program, you can determine whether you want the delete report to start in either test or production mode. In the archiving object-specific Customizing, you can activate the automatic start of the delete program. When delivery processing executes the delete program, it records a log containing information about the processed data records. In the selection screen of the delete program, you can define that a detailed log is to be displayed in delivery processing. In addition to the information contained in the log, this contains all processed objects including the associated messages.

Read The read program reads the archived data records.

SAP Extended Warehouse Management (SAP EWM)

510

1026

SAP Online Help

20.07.2007

In the selection screen of the read program, you can select the documents to be archived using the selection criteria in Deliveries and Restrictions. In the search type, you can define whether the data records are to be searched for via the Archive Information System [Extern] or sequentially. Sequential Search The sequential search depends on the size of the archive file since all documents in this file have to be read by the system. Search via Archive Information System The search using the Archive Information System is based on index tables and is faster than the sequential search. However, you have to specify the document number to use this search. If you want to use the search via the Archive Information System, you must first activate the archive information structure SAP_DLV_PROCH_I in the Archive Retrieval Configurator (ARC) (see Activating and Deactivating Information Structures [Extern]). Display of Archived Data Records In the archiving administration, the system only displays the header data of the documents. The complete document data can be displayed via the relevant user interface that is assigned to delivery processing. You can use a search function on the user interface to display the archived documents with all the detailed data.

We recommend that you use read program /SCDL/DLV_INB_ACRH_READ for reading archived data records for test purposes only. Instead, use the search function on the relevant user interface. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing → Inbound Delivery → Maintain Inbound Delivery and then choose the Open Advanced Search pushbutton. On the Search Crit. 2 tab page, choose Archive as the data source. The system displays the normal document display with all the data records.

For more information about archiving objects, see Data Archiving (CA-ARC) in the section Archiving Object [Extern]. For more information about the procedure for writing, deleting, and reading data records, see Archiving Procedure [Extern] in data archiving (CA-ARC).

SAP Extended Warehouse Management (SAP EWM)

510

1027

SAP Online Help

20.07.2007

Archiving Internal Warehouse Requests (SCMECT-DLP) Definition Archiving object DLV_OUT for the archiving and deletion of outbound delivery orders [Seite 91], outbound deliveries [Seite 93], posting changes [Seite 128], and stock transfers within the warehouse [Seite 122].

Structure The following programs are available for DLV_OUT: Program

Function

/SCDL/DLV_OUT_ARCH_WRITE

Write

/SCDL/DLV_OUT_ARCH_DELETE

Delete

/SCDL/DLV_OUT_ACRH_READ

Read

Write The write program reads the data records of the documents to be archived from the database and records them in an archive file. In the selection screen of the write program, you can select the documents to be archived via the selection criteria in Deliveries and Restrictions. In the process control, you can determine whether you want the write report to start in either test or production mode. If you have activated the automatic start of the deletion program in archiving-object-specific Customizing, you can also define here that delivery processing starts the deletion program of the archiving object with the test mode variant saved in archiving-object-specific Customizing. When delivery processing executes the write program, it records a log containing information about the processed data records. In the selection screen of the write program, you can define that a detailed log is to be displayed in delivery processing. In addition to the information contained in the log, this contains all processed objects including the associated messages. Prerequisites for Writing Data Records The documents to be archived must have the status To Be Archived (see Archiving in Delivery Processing [Seite 1024]).

Delete The delete program deletes the data records from the database that were previously archived with the write program. In the selection screen of the delete program, you can determine whether you want the delete report to start in either test or production mode. In the archiving object-specific Customizing, you can activate the automatic start of the delete program. When delivery processing executes the delete program, it records a log containing information about the processed data records. In the selection screen of the delete program, you can define that a detailed log is to be displayed in delivery processing. In addition to the information contained in the log, this contains all processed objects including the associated messages.

Read The read program reads the archived data records.

SAP Extended Warehouse Management (SAP EWM)

510

1028

SAP Online Help

20.07.2007

In the selection screen of the read program, you can select the documents to be archived via the selection criteria in Deliveries and Restrictions. In the search type, you can define whether the data records are to be searched for via the Archive Information System [Extern] or sequentially. Sequential Search The sequential search depends on the size of the archive file since all documents in this file have to be read by the system. Search via Archive Information System The search using the Archive Information System is based on index tables and is faster than the sequential search. However, you have to specify the document number to use this search. If you want to use the search via the Archive Information System, you must first activate the relevant archive information structure for each document category in the Archive Retrieval Configurator (ARC) (see Activating and Deactivating Information Structures [Extern]). The following archive information structures are available for DLV_OUT: Archive Information Structure

Document Category

SAP_DLV_FDH

Outbound Delivery

SAP_DLV_PROCH_O

Outbound Delivery Order, Posting Change, Stock Transfer Within Warehouse

Display of Archived Data Records In the archiving administration, the system only displays the header data of the documents. The complete document data can be displayed via the relevant user interface that is assigned to delivery processing. You can use a search function on the user interface to display the archived documents with all the detailed data.

We recommend that you use read program /SCDL/DLV_INB_ACRH_READ for reading archived data records for test purposes only. Instead, use the search function on the relevant user interface. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing and one of the following options: → Outbound Delivery → Maintain Outbound Delivery Order and the Open Advanced Search pushbutton. On the Search Crit. 2 tab page, choose Archive as the data source. → Maintain Outbound Delivery and the Open Advanced Search pushbutton. On the Search Crit. 2 tab page, choose Archive as the data source. → Posting Change → Maintain Posting Change and the Open Advanced Search pushbutton. Choose Archive as the data source. → Maintain Internal Stock Transfer and the Open Advanced Search pushbutton. Choose Archive as the data source. The system displays the normal document display with all the data records.

For more information about archiving objects, see Data Archiving (CA-ARC) in the section Archiving Object [Extern]. For more information about the procedure for writing, deleting, and reading data records, see Archiving Procedure [Extern] in data archiving (CA-ARC).

SAP Extended Warehouse Management (SAP EWM)

510

1029

SAP Online Help

20.07.2007

Archiving Warehouse Requests from External Systems (SCM-ECT-DLP) Definition Archiving object DLV_REQ for archiving and deleting inbound delivery notifications [Seite 87], outbound delivery requests [Seite 90], and posting change requests [Seite 128].

Structure The following programs are available for DLV_REQ: Program

Function

/SCDL/DLV_REQ_ARCH_WRITE

Write

/SCDL/DLV_REQ_ARCH_DELETE

Delete

/SCDL/DLV_REQ_ACRH_READ

Read

Write The write program reads the data records of the documents to be archived from the database and records them in an archive file. In the selection screen of the write program, you can select the documents to be archived using the selection criteria in Deliveries and Restrictions. In the process control, you can determine whether you want the write report to start in either test or production mode. If you have activated the automatic start of the deletion program in archiving-object-specific Customizing, you can also define here that delivery processing starts the deletion program of the archiving object with the test mode variant saved in archiving-object-specific Customizing. When delivery processing executes the write program, it records a log containing information about the processed data records. In the selection screen of the write program, you can define that a detailed log is to be displayed in delivery processing. In addition to the information contained in the log, this contains all processed objects including the associated messages. Prerequisites for Writing Data Records The documents to be archived must have the status To Be Archived (see Archiving in Delivery Processing [Seite 1024]).

Delete The delete program deletes the data records from the database that were previously archived with the write program. In the selection screen of the delete program, you can determine whether you want the delete report to start in either test or production mode. In the archiving object-specific Customizing, you can activate the automatic start of the delete program. When delivery processing executes the delete program, it records a log containing information about the processed data records. In the selection screen of the delete program, you can define that a detailed log is to be displayed in delivery processing. In addition to the information contained in the log, this contains all processed objects including the associated messages.

Read The read program reads the archived data records.

SAP Extended Warehouse Management (SAP EWM)

510

1030

SAP Online Help

20.07.2007

In the selection screen of the read program, you can select the documents to be archived using the selection criteria in Deliveries and Restrictions. In the search type, you can define whether the data records are to be searched for via the Archive Information System [Extern] or sequentially. Sequential Search The sequential search depends on the size of the archive file since all documents in this file have to be read by the system. Search via Archive Information System The search using the Archive Information System is based on index tables and is faster than the sequential search. However, you have to specify the document number to use this search. If you want to use the search via the Archive Information System, you must first activate the archive information structure SAP_DLV_REQH in the Archive Retrieval Configurator (ARC) (see Activating and Deactivating Information Structures [Extern]). Display of Archived Data Records In the archiving administration, the system only displays the header data of the documents. The complete document data can be displayed via the relevant user interface that is assigned to delivery processing. You can use a search function on the user interface to display the archived documents with all the detailed data.

We recommend that you use read program /SCDL/DLV_INB_ACRH_READ for reading archived data records for test purposes only. Instead, use the search function on the relevant user interface. To do so, on the SAP Easy Access screen, choose Extended Warehouse Management → Delivery Processing and one of the following options: → Inbound Delivery → Maintain Inbound Delivery Notification and the Open Advanced Search pushbutton. On the Search Crit. 2 tab page, choose Archive as the data source. → Outbound Delivery → Maintain Outbound Delivery Request and the Open Advanced Search pushbutton. On the Search Crit. 2 tab page, choose Archive as the data source. → Posting Change → Maintain Posting Change Request and the Open Advanced Search pushbutton. Choose Archive as the data source. The system displays the normal document display with all the data records.

For more information about archiving objects, see Data Archiving (CA-ARC) in the section Archiving Object [Extern]. For more information about the procedure for writing, deleting, and reading data records, see Archiving Procedure [Extern] in data archiving (CA-ARC).

SAP Extended Warehouse Management (SAP EWM)

510

1031

SAP Online Help

20.07.2007

Archiving in Quality Management Use You can use archiving to remove data records for inspection documents [Extern] in quality management (QM), from the database that are no longer required in the system. Here, QM uses archiving object QIE_INSP to archive inspection documents and dependent objects of the Quality Inspection Engine component (CA-QIE).

Integration Quality management uses the central data archiving functions. For more information on this service, see Introduction to Data Archiving (CA-ARC) [Seite 1020].

Features Each document category is assigned to an archiving object that contains exact information about which data the system is to archive and how. The following table shows the document categories and the relevant archiving objects for quality management: Document Category

Archiving Object

Inspection document

QIE_INSP [Seite 1033]

The archiving objects provide a series of actions that you can use for the data records in archive administration (transaction SARA).

Actions For more information about the procedure for writing, deleting, and reading data records, see Archiving Procedure [Extern] in data archiving (CA-ARC).

SAP Extended Warehouse Management (SAP EWM)

510

1032

SAP Online Help

20.07.2007

Archiving - Inspection Documents (CA-QIE) The archiving object QIE_INSP is used for archiving inspection documents and dependent objects in the component Quality Inspection Engine (CA-QIE).

You can use the archiving object QIE_INSP to archive inspection documents and their dependent objects if you no longer require direct access to these. Dependent objects are samples, items, and findings. You can display the archived data in the corresponding display transaction in the consumer system, but you cannot reload the data.

Structure If you use the archiving object QIE_INSP, data from the following tables, among others, is archived: Table to be archived QIE_INSP_DOC

Short description Inspection document

QIE_INSP_DOC_ES Document data for the inspection document in the external system QIE_INSP_DOC_EX Inspection data and results data for the inspection document QIE_INSP_DOC_IX

Index of inspection object properties for the inspection document

QIE_ELEMENT

Elements (samples and items)

QIE_ELEMENT_IX

Index for elements

QIE_FIND_CODE

Additional codes for finding

QIE_FINDING

Findings

QIE_ASSIGN

QIE: Links

QIE_DOC_ASSIGN

Document assignment

The following archiving classes, among others, are involved: Archiving Class

Short Description

QIE_INSP_D

Inspection document

QIE_INSP_E

Elements (samples and items)

QIE_CONF_F

Findings

QIE_DOC_AS

Document assignment

CRM_STATUS

Status objects (GUID-based status management)

SAP Extended Warehouse Management (SAP EWM)

510

1033

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

1034

SAP Online Help

20.07.2007

Inspections (CA-QIE) During preprocessing, the system checks that: •

The inspection document and its dependent objects are not in processing.

•

The inspection document has the status To Be Archived (I1855) or Cancelled (I1854).

•

The inspection document has none of the above statuses, but it has been completed and the number of days since the last change has expired. You define the number of days in the selection conditions of the report.

•

The checks that you implemented in the Business Add-In (BAdI) Own Checks for Archiving Object QIE_INSP (ARC_QIE_INSP_CHECK) had positive results.

•

The status of the inspection document allows the operations Flag for Archiving (QE07) and Archive (QE09).

SAP Extended Warehouse Management (SAP EWM)

510

1035

SAP Online Help

20.07.2007

Application Customizing (CA-QIE) In Application Customizing, you can adjust the settings for the execution of archiving runs. Under Archiving, you can create and activate implementations for the following Business AddIns (BAdIs): •

You can use the BAdI Own Inspections for Archiving Object QIE_INSP (ARC_QIE_INSP_CHECK) to set up additional checks in preprocessing. You can use this BAdI, among other things, to differentiate between the number of days since the last change of the different inspection object types.

•

You can use the BAdI Own Data for Archiving Object QIE_INSP (ARC_QIE_INSP_WRITE) to archive and delete own data. The BAdI is called in the archiving and deletion runs.

SAP Extended Warehouse Management (SAP EWM)

510

1036

SAP Online Help

20.07.2007

Preprocessing: Editing Variants (CA-QIE) You can use the preprocessing program to set the status To Be Archived or Archived for inspection documents. This status is a prerequisite for archiving. Note It is not possible to change inspection documents that have the status To Be Archived or Archived. End of the note.

Procedure 1. Choose

Tools Administration Administration Data Archiving

.

2. Enter the archiving object QIE_INSP and confirm your entry. 3. Choose Preprocessing. 4. Enter a report variant on the Preprocessing screen. If no variant exists, choose Maintain to maintain the required variant. If you choose Detailed Log on the selection screen, the system returns a log line for every archived inspection document. 5. Enter the start date and the spool parameters. You use the spool parameters to control the print output of the preprocessing log that is generated. 6. Select Execute on the initial screen. 7. You can access information about the status of the preprocessing job in the job overview. You can also display the log in the job overview after the job has been completed.

Result The preprocessing program sets the status To Be Archived or Archived for inspection documents. The preprocessing program creates a log and, if required, a detailed log. After the preprocessing run, you can archive inspection documents that you have flagged.

SAP Extended Warehouse Management (SAP EWM)

510

1037

SAP Online Help

20.07.2007

Writing: Editing Variants (CA-QIE) The archiving program writes the data records of the archiving object QIE_INSP to the archive.

Prerequisites Before you start the archiving run, you must flag inspection documents for archiving using the preprocessing run.

Procedure 1. Choose

Tools Administration Administration Data Archiving

.

2. Enter the archiving object QIE_INSP and choose Write. 3. Enter a report variant on the Create Archive Files screen. If no variant exists, choose Maintain to maintain the required variant. If you choose Detailed Log on the selection screen, the system returns a log line for every archived inspection document. 4. Enter the start date and the spool parameters. You use the spool parameters to control the print output of the archiving log that is generated. 5. Select Execute on the initial screen. 6. You can access information about the status of the archiving job in the job overview. You can also display the log in the job overview after the job has been completed.

Result The data of the selected inspection documents is archived. The archiving program creates a log and, if required, a detailed log. If you specify that the deletion job should start automatically in archiving object-specific Customizing, the system will start the deletion job automatically after archiving has taken place. If the deletion job is not started automatically, you must start it manually.

SAP Extended Warehouse Management (SAP EWM)

510

1038

SAP Online Help

20.07.2007

Deleting: Editing Variants (CA-QIE) The deletion program deletes the data records for the archiving object QIE_INSP.

Prerequisites Before you start the deletion run, you must archive the inspection documents using the archiving run.

Procedure 1. Choose

Tools Administration Administration Data Archiving

.

2. On the initial screen of archive administration, enter the archiving object QIE_INSP and choose Delete. 3. On the Execeute Delete Program screen, choose one or more archiving runs using the archive selection. 4. Maintain the start date and the spool parameters. You use the spool parameters to control the print output of the deletion log that is generated. If you choose Detailed Log on the selection screen, the system returns a log line for every archived inspection document. 5. Select Execute on the initial screen. 6. You can access information about the status of the deletion job in the job overview. You can also display the log in the job overview after the job has been completed.

Result The data for the selected archiving runs is deleted. The deletion program creates a log and, if required, a detailed log. You can display the deleted data in the consumer system of the QIE using the corresponding display transactions or using the Archive Explorer.

SAP Extended Warehouse Management (SAP EWM)

510

1039

SAP Online Help

20.07.2007

Authorizations (CA-QIE) To display the programs for archiving the archiving object QIE_INSP, you need the authorization S_ARCHIVE. To display the archived data, you need authorization for the Archive Information System or for the display transaction in the consumer system.

SAP Extended Warehouse Management (SAP EWM)

510

1040

SAP Online Help

20.07.2007

Log (CA-QIE) When you execute the various archiving programs, the system creates logs in list form. If you execute the programs in the background, the system uses the print output and outputs the logs via spool requests. The logs contain information, for example, about which inspection documents were selected or how many inspection documents were processed.

Prerequisites The logs are output after the preprocessing, archiving, and deletion runs.

Features The system creates different logs for each of the three archiving steps. To display the selection conditions, you may have to select the selection cover sheet in the spool settings.

Preprocessing Log On the selection screen, you can choose between a summarized and a detailed log. The system displays the following information: •

Selection criteria

•

Number of objects in the list of hits that were retrieved based on the selection conditions

•

Number of selected inspection documents for which the status archived can be set

Archiving Log On the selection screen, you can choose between a summarized and a detailed log. For a summarized log, the system displays the following information: •

Selection criteria

•

Key of the archive file and number of the archiving run

•

Statistical key figures for the archived database tables

•

Number of inspection documents to be archived

Deletion Log On the selection screen, you can choose between a summarized and a detailed log. The system displays the following information: •

Indicator for test mode or productive mode

•

Keys of archive files

•

Number of deleted objects

•

Number of deleted records for every relevant database table

If outputting a detailed log, the system also shows the following information for every archived object: SAP Extended Warehouse Management (SAP EWM)

510

1041

SAP Online Help •

External number of the inspection document

•

Success or failure messages

20.07.2007

Note You should only select the detailed log for small quantities of data, for example, in test mode for just a few objects. If you select too much data, the system could terminate due to memory overflow. End of the note.

Activities •

You must specify suitable spool parameters before you execute an archiving program.

•

The log is created automatically by the system after the program has been executed.

•

You can display the log using the job overview. You can also display it under Display Spool List Display Contents .

SAP Extended Warehouse Management (SAP EWM)

510

1042

SAP Online Help

20.07.2007

Displaying Archived Inspection Documents (CAQIE) You can display archived and deleted inspection documents in the consumer system.

Activities In the consumer system, call the display transaction for inspection documents and enter the number of the archived and deleted inspection document. You can also use the Archive Explorer to access the technical view of the archived inspection document.

SAP Extended Warehouse Management (SAP EWM)

510

1043

SAP Online Help

20.07.2007

Archiving in Shipping and Receiving Use You can use archiving to remove data records for shipping and receiving activities [Seite 624] from the database that are no longer required in the system.

Integration Shipping and receiving uses the central data archiving functions. For more information, see Introduction to Data Archiving (CA-ARC) [Seite 1020].

Features Each document category is assigned to an archiving object [Extern] that contains exact information about which data the system is to archive and how. The following table shows the document categories and the relevant archiving objects for shipping and receiving: Document Category

Archiving Object

Door Activities

WME_DOOR [Seite 1052]

Vehicle Activities

WME_VEH [Seite 1045]

TU Activities

WME_TU [Seite 1048]

The archiving objects provide a series of actions that you can use for the data records in archive administration (transaction SARA).

SAP Extended Warehouse Management (SAP EWM)

510

1044

SAP Online Help

20.07.2007

Archiving Vehicle Activities (SCM-EWM-SR) Definition Archiving object WME_VEH for archiving and deleting shipping and receiving activities [Seite 624] for vehicles [Seite 612] (vehicle activities).

Structure Tables Extended Warehouse Management (EWM) uses the archiving object WME_VEH to archive data from the following tables: Table

Description

Explanation

/SCWM/VEHICLE

Vehicle

This database table contains the data for the vehicle itself.

/SCWM/VEH_IDENT

Table with Vehicle Identifications

This database table contains identifiers. Each vehicle activity can be mapped externally by multiple identifiers.

/SCWM/VEH_SR_ACT

S&R Activities of a Vehicle

This database table contains start dates/times and end dates/times. Each vehicle activity is defined by its start date/time and end date/time.

/SCWM/VEH_STATUS

Status of Vehicle Activities

This database table contains statuses. The progress of each individual vehicle activity is described by various statuses.

Programs The following programs are available for WME_VEH: Program

Function

WME_ARCH_VEH_MARK

Mark only (preprocessing program)

WME_ARCH_VEH_WRITE

Write only

WME_ARCH_VEH_MARK_AND_WRITE

Mark and write

WME_ARCH_VEH_DELETE

Delete

WME_ARCH_VEH_READ

Read and display

Write Before the system writes vehicle activities to archive files, it changes the status from Archivable to Archived. You can no longer process archived vehicle activities. The system archives the following data for each vehicle activity: ●

Relevant vehicle data

●

All status entries

●

All identifiers

SAP Extended Warehouse Management (SAP EWM)

510

1045

SAP Online Help

20.07.2007

Prerequisites for writing vehicle activities Vehicle activities must have the status Archivable in order for the system to be able to archive them. The system flags a vehicle activity with the status Archivable if the following conditions have been met: ●

The activity end was at least 60 days ago (fixed value).

●

No transportation units (TUs) are assigned to the vehicle activity any more.

Delete After writing the archive files, the system performs a test run where it reads the data in the archive files and compares it with the data in the database. If it does not find any differences, the system deletes the database data.

Although the system always archives vehicle master data (/SCWM/VEHICLE), it only deletes it from the database if the following conditions have been met: ■

No other vehicle activities still exist.

■

You have not set the indicator for permanent vehicles.

Read The system uses the selection options to search for suitable activity data in the data sources. The following table shows the selection criteria available: Text

Database Table

Field

Internal Vehicle Number

/SCWM/VEH_SR_ACT

VEH_NUM

External Vehicle Number

/SCWM/VEHICLE

VEH_NUM_EXT

License Plate Number

/SCWM/VEH_SR_ACT

LIC_PLATE

Transportation Service Provider

/SCWM/VEH_SR_ACT

TSP_CURR

Actual Activity Start

/SCWM/VEH_SR_ACT

START_ACTUAL

Actual Activity End

/SCWM/VEH_SR_ACT

END_ACTUAL

You can choose the following data sources: ●

Database

●

Archive file chosen manually

●

Archive Information System (AS) [Extern]

If you choose all three data sources and the system has archived a vehicle activity multiple times without deleting it, the system searches through the data sources in the following order: ...

1. The system reads the vehicle activity from the database. 2. The system reads the vehicle activity from the archive file chosen manually, as appropriate, and overwrites the version found previously. 3. The system uses the AS to search for the vehicle activity in multiple archive files, reads it, and overwrites the version found previously. The last source that is found determines which data is displayed (in particular for the vehicle master data).

SAP Extended Warehouse Management (SAP EWM)

510

1046

SAP Online Help

20.07.2007

Display A list of the vehicle activities found is displayed. The cursor position determines the current vehicle activity. You can use the Details pushbutton to display this current vehicle activity as a form.

Only fields for which you have defined values are displayed in this form. The system suppresses fields with initial field values. You can display the following dependent data for the current vehicle activity: ●

Data record with general vehicle data (Vehicle Master Data pushbutton)

●

Table with the relevant status entries (Status pushbutton)

●

Table with the external identifiers assigned to the vehicle activity (Identifiers pushbutton)

●

Assignments of the vehicle activity to one or more shipping and receiving activities for transportation units (TU activities) (Vehicle TU pushbutton)

You can use the Vehicle Activities pushbutton to return to the activity table.

If you double-click the individual pushbuttons, you can display all the data records read, irrespective of the current vehicle activity. You can use the Details pushbutton to display the data in the format of a form.

Variant Settings for Preprocessing As the selection criterion, you can specify the number of days that must have passed since the vehicle activities were completed (default value: 60 days).

Integration Display Function for Archived Vehicle Activities You can use the following field catalog and archive information structure to access archived vehicle activities using the Archive Information System: ●

Field catalog SAP_WME_VEH

●

Archive information structure SAP_WME_VEH

SAP Extended Warehouse Management (SAP EWM)

510

1047

SAP Online Help

20.07.2007

Archiving TU Activities (SCM-EWM-SR) Definition Archiving object WME_TU for archiving and deleting shipping and receiving activities [Seite 624] for transportation units [Seite 613] (TU activities).

Structure Tables Extended Warehouse Management (EWM) uses the archiving object WME_TU to archive data from the following tables: Table

Description

Explanation

/SCWM/TU_DLV

Assignment of Deliveries and HUs to Transportation Units

This database table shows the relationship between the TU activity and its contents (deliveries).

/SCWM/TU_DOOR

Assignment of Transportation Units to Doors

This database table contains the relationships between TU activities and door activities.

/SCWM/TU_IDENT

Table with TU Identifications

This database table contains identifiers. Each TU activity can be mapped externally by multiple identifiers.

/SCWM/TUNIT

Transportation Unit

This database table contains the data for the transportation unit (TU) itself.

/SCWM/TUNIT_SEAL

Seal for Transportation Units

This database table contains seal information for each TU activity.

/SCWM/TU_SR_ACT

S&R Activity of a Transportation Unit

This database table contains start dates/times and end dates/times. Each TU activity is defined by its start date/time and end date/time.

/SCWM/TU_STATUS

Status of Transportation Unit Activities

This database table contains statuses. The progress of each individual TU activity is described by various statuses.

/SCWM/TU_VEH

Assignment of Transportation Units to Vehicles

This database table contains one or more vehicle activities with which a TU activity can be linked.

Each TU is connected to the stock information via a virtual handling unit (HU). The system deletes this HU as soon as the TU has been deleted. The system does not archive the HU information.

SAP Extended Warehouse Management (SAP EWM)

510

1048

SAP Online Help

20.07.2007

Programs The following programs are available for WME_TU: Program

Function

WME_ARCH_TU_MARK

Mark only (preprocessing program)

WME_ARCH_TU_WRITE

Write only

WME_ARCH_TU_MARK_AND_WRITE

Mark and write

WME_ARCH_TU_DELETE

Delete

WME_ARCH_TU_READ

Read and display

Write Before the system writes TU activities to archive files, it changes the status from Archivable to Archived. You can no longer process archived TU activities. The system archives the following data for each TU activity: ●

Relevant TU data

●

All status entries

●

All identifiers

●

All seal information

●

All assignments to door activities

●

All assignments to vehicle activities

●

All assignments to deliveries

Prerequisites for writing TU activities TU activities must have the status Archivable in order for the system to be able to archive them. The system flags a TU activity with the status Archivable if the following conditions have been met: ●

The activity end was at least 60 days ago (fixed value).

●

No stock is still assigned to the TU activity in Logistics Inventory Management Engine (LIME).

Delete After writing the archive files, the system performs a test run where it reads the data in the archive files and compares it with the data in the database. If it does not find any differences, the system deletes the database data.

Although the system always archives TU master data (/SCWM/TUNIT), it only deletes it from the database if the following condition has been met: ■

No other TU activities still exist.

When the system deletes the TU itself, the relevant HU information is also deleted automatically. Read The system uses the selection options to search for suitable activity data in the data sources. The following table shows the selection criteria available: Text

Table

SAP Extended Warehouse Management (SAP EWM)

Field

510

1049

SAP Online Help

20.07.2007

Internal TU Number

/SCWM/TU_SR_ACT

TU_NUM

External TU Number

/SCWM/TUNIT

TU_NUM_EXT

License Plate Number

/SCWM/TU_SR_ACT

LIC_PLATE

Transportation Service Provider

/SCWM/TU_SR_ACT

TSP_CURR

Actual Activity Start

/SCWM/TU_SR_ACT

START_ACTUAL

Actual Activity End

/SCWM/TU_SR_ACT

END_ACTUAL

You can choose the following data sources: ●

Database

●

Archive file chosen manually

●

Archive Information System (AS) [Extern]

If you choose all three data sources and the system has archived a TU activity multiple times without deleting it, the system searches through the data sources in the following order: ...

1. The system reads the TU activity from the database. 2. The system reads the TU activity from the archive file chosen manually, as appropriate, and overwrites the version found previously. 3. The system uses the AS to search for the TU activity in multiple archive files, reads it, and overwrites the version found previously. The last source that is found determines which data is displayed (in particular for the TU master data). Display A list of the TU activities found is displayed. The cursor position determines the current TU activity. You can use the Details pushbutton to display this current TU activity as a form.

Only fields for which you have defined values are displayed in this form. The system suppresses fields with initial field values. You can display the following dependent data: ●

Data record with general TU data (TU Master Data pushbutton)

●

Table with the relevant status entries (Status pushbutton)

●

Table with the external identifiers assigned to the TU activity (Identifiers pushbutton)

●

Table with the seal information assigned to the TU activity (Seal pushbutton)

●

Table with the door activities assigned to the TU activity (TU Door pushbutton)

●

Table with the deliveries assigned to the TU activity (TU Delivery pushbutton)

●

Assignments of the TU activity to one or more vehicle activities (TU Vehicle pushbutton)

You can use the TU Activities pushbutton to return to the activity table.

If you double-click the individual pushbuttons, you can display all the data records read, irrespective of the current TU activity. You can use the Details pushbutton to display the data in the format of a form.

SAP Extended Warehouse Management (SAP EWM)

510

1050

SAP Online Help

20.07.2007

Variant Settings for Preprocessing As the selection criterion, you can specify the number of days that must have passed since the TU activities were completed (default value: 60 days).

Integration Display Function for Archived TU Activities You can use the following field catalog and archive information structure to access archived TU activities using the Archive Information System: ●

Field catalog SAP_WME_TU

●

Archive information structure SAP_WME_TU

SAP Extended Warehouse Management (SAP EWM)

510

1051

SAP Online Help

20.07.2007

Archiving Door Activities (SCM-EWM-SR) Definition Archiving object WME_DOOR for archiving and deleting door activities, in other words, shipping and receiving activities [Seite 624] for doors [Seite 32] (door activities).

Structure Tables Extended Warehouse Management (EWM) uses the archiving object WME_DOOR to archive data from the following tables: Table

Description

Explanation

/SCWM/DOOR_SRACT

S&R Activities of a Door

This database table contains start dates/times and end dates/times. Each door activity is defined by its start date/time and end date/time.

/SCWM/TDOOR

Door Definition with Assignment to Staging Areas and Yard

This database table contains a master data record with the data for the door itself. This data does not refer to the individual door activities.

Programs The following programs are available for WME_DOOR: Program

Function

WME_ARCH_DOOR_MARK

Mark only (preprocessing program)

WME_ARCH_DOOR_WRITE

Write only

WME_ARCH_DOOR_MARK_AND_WRITE

Mark and write

WME_ARCH_DOOR_DELETE

Delete

WME_ARCH_DOOR_READ

Read and display

Write Before the system writes door activities to archive files, it changes the status from Archivable to Archived. You can no longer process archived door activities. The system archives only the relevant door data for each door activity. Prerequisites for writing door activities Door activities must have the status Archivable in order for the system to be able to archive them. The system flags a door activity with the status Archivable if the following conditions have been met: ●

The activity end was at least 60 days ago (fixed value).

●

No transportation units (TUs) are assigned to the door activity any more.

Delete After writing the archive files, the system performs a test run where it reads the data in the archive files and compares it with the data in the database. If it does not find any differences, the system deletes the database data.

SAP Extended Warehouse Management (SAP EWM)

510

1052

SAP Online Help

20.07.2007

Although the system always archives the door master data (/SCWM/TDOOR), it never deletes it from the database (door data is Customizing data). Read The system uses the selection options to search for suitable activity data in the data sources. The following table shows the selection criteria available: Text

Table

Field

Warehouse Number

/SCWM/DOOR_SRACT

LGNUM

Door Number

/SCWM/DOOR_SRACT

DOOR

Actual Activity Start

/SCWM/DOOR_SRACT

START_ACTUAL

Actual Activity End

/SCWM/DOOR_SRACT

END_ACTUAL

You can choose the following data sources: ●

Database

●

Archive file chosen manually

●

Archive Information System (AS) [Extern]

If you choose all three data sources and the system has archived a door activity multiple times without deleting it, the system searches through the data sources in the following order: ...

1. The system reads the door activity from the database. 2. The system reads the door activity from the archive file chosen manually, as appropriate, and overwrites the version found previously. 3. The system uses the AS to search for the door activity in multiple archive files, reads it, and overwrites the version found previously. The last data source that is found determines which data is displayed (in particular for the door master data). Display A list of the door activities found is displayed. The cursor position determines the current door activity. You can use the Details pushbutton to display this current door activity as a form.

Only fields for which you have defined values are displayed in this form. The system suppresses fields with initial field values. You can display the following dependent data for the current door activity: ●

Data record with general door data (Door Master Data pushbutton)

●

Assignments of the door activity to one or more shipping and receiving activities for transportation units (TUs) (TU Assignments pushbutton)

You can use the Door Activities pushbutton to return to the activity table.

If you double-click the individual pushbuttons, you can display all the data records read, irrespective of the current door activity. You can use the Details pushbutton to display the data in the format of a form.

Variant Settings for Preprocessing As the selection criterion, you can specify either the warehouse number or the number of days that must have passed since the door activities were completed (default value: 60 days).

SAP Extended Warehouse Management (SAP EWM)

510

1053

SAP Online Help

20.07.2007

Integration Display Function for Archived Door Activities You can use the following field catalog and archive information structure to access archived door activities using the Archive Information System: ●

Field catalog SAP_WME_DOOR

●

Archive information structure SAP_WME_DOOR

SAP Extended Warehouse Management (SAP EWM)

510

1054

SAP Online Help

20.07.2007

Archiving in Transportation Management Use You can use archiving to remove data records for documents from the database that are no longer required in Transportation Management (TM).

Integration Transportation Management uses the central data archiving functions. For more information, see Introduction to Data Archiving (CA-ARC) [Seite 1020].

Prerequisites You have defined the following in Customizing for TM: ●

Residence time [Extern]

●

Time unit for the residence time

For more information, see the Implementation Guide (IMG) for Extended Warehouse Management (EWM) under Goods Issue Process → Transportation Management → Shipments → Define Shipment Type or Freight Documents → Define Freight Document Type.

Features Each document category is assigned to an archiving object [Extern] that contains exact information about which data the system is to archive and how. The following table shows document categories and the relevant archiving objects for Transportation Management: Document Category

Archiving Object

Shipment

TM_SHP [Seite 1056]

Freight Document

TM_FRD [Seite 1058]

The archiving objects provide a series of actions that you can use in the archive administration (transaction SARA) for the data records in TM. The system must perform checks before it can archive shipments and freight documents. For example, it checks whether the residence time was exceeded. You define the residence time for each freight document type and each shipment type. The system calculates it as follows: ●

Current date minus creation date

●

Current date minus date of the last change

For shipments and freight documents that have not been changed, the date of the last change is the creation date.

SAP Extended Warehouse Management (SAP EWM)

510

1055

SAP Online Help

20.07.2007

Archiving Shipments (SCM-EWM-TM) Definition Archiving object TM_SHP for archiving and deleting shipments [Seite 630].

Structure Tables Extended Warehouse Management (EWM) uses the archiving object TM_SHP to archive data from the following tables: Table

Description

CDCLS

Cluster Structure for Change Documents

CDHDR

Change Document Header

CDPOS_STR

Additional Change Document - Table for Strings

CDPOS_UID

Additional Table for Inclusion of TABKEY > 70 Characters

STXB

SAPscript: Texts in non-SAPscript Format

STXH

STXD SAPscript Text File Header

STXL

STXD SAPscript Text File Lines

Programs The following programs are available for TM_SHP: Program

Function

/SCTM/R_SHP_ARCHIVE_WRITE

Write

/SCTM/R_SHP_ARCHIVE_DELETE

Delete

/SCTM/R_SHP_ARCHIVE_RELOAD

Reload

Prerequisites for writing shipments If the following prerequisites are met, the system can archive a shipment: ●

The document was in the database for the duration of the residence time.

●

The document has the status Transportation Completed.

Variant Settings for Writing You can specify planned shipments or final shipments as the selection criteria.

Integration Display Function for Archived Shipments You can use the following field catalog and archive information structure to access archived shipments using the Archive Information System [Extern]: ●

Field catalog SAP_TM_SHP

●

Archive information structure SAP_TM_SHP

SAP Extended Warehouse Management (SAP EWM)

510

1056

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

1057

SAP Online Help

20.07.2007

Archiving Freight Documents (SCM-EWM-TM) Definition Archiving object TM_FRD for archiving and deleting freight documents [Seite 632].

Structure Tables Extended Warehouse Management (EWM) uses the archiving object TM_FRD to archive data from the following tables: Table

Description

CDCLS

Cluster Structure for Change Documents

CDHDR

Change Document Header

CDPOS_STR

Additional Change Document - Table for Strings

CDPOS_UID

Additional Table for Inclusion of TABKEY > 70 Characters

STXB

SAPscript: Texts in non-SAPscript Format

STXH

STXD SAPscript Text File Header

STXL

STXD SAPscript Text File Lines

Programs The following programs are available for TM_FRD: Program

Function

/SCTM/R_FRD_ARCHIVE_WRITE

Write

/SCTM/R_FRD_ARCHIVE_DELETE

Delete

/SCTM/R_FRD_ARCHIVE_RELOAD

Reload

Prerequisites for writing freight documents If the following prerequisites are met, the system can archive a freight document: ●

The document was in the database for the duration of the residence time.

●

The document has the status Transportation Ended.

Integration Display Function for Archived Freight Documents You can use the following field catalog and archive information structure to access archived freight documents using the Archive Information System [Extern]: ●

Field catalog SAP_TM_FRD

●

Archive information structure SAP_TM_FRD

SAP Extended Warehouse Management (SAP EWM)

510

1058

SAP Online Help

20.07.2007

Archiving for Value-Added Services Use You can use archiving to remove data records for value-added services orders from the database that are no longer required for value-added services.

Integration The standard data archiving solution is used for archiving value-added services orders. For more information, see Introduction to Data Archiving (CA-ARC) [Seite 1020].

Features Each document category is assigned to an archiving object [Extern] that contains exact information about which data the system is to archive and how. The following table shows the document categories and the relevant archiving objects for value-added services: Document Category

Archiving Object

Value-Added Service Orders

WME_VAS [Seite 1060]

The archiving objects provide a series of actions that you can use for the data records in the archive administration (transaction SARA).

Activities For more information about the procedure for writing, deleting, and reading data records, see Archiving Procedure [Extern] in data archiving (CA-ARC).

SAP Extended Warehouse Management (SAP EWM)

510

1059

SAP Online Help

20.07.2007

Archiving Value-Added Service Orders (SCMEWM-VAS) Definition You use the archiving object WME_VAS to archive value-added service orders.

Use You can archive value-added service orders that Extended Warehouse Management (EWM) saved a certain number of days ago. You can also simultaneously archive value-added service orders for multiple warehouse numbers. For test purposes, you can display a list of all the value-added service orders to be archived and deleted before archiving them.

Structure Tables Order document management (ODM) generates the database tables from which data is archived.

Programs The following programs are delivered for the archiving object WME_VAS: Programs

Function

WME_ARCH_VAS_WRITE

Write

WME_ARCH_VAS_DELETE

Delete

WME_ARCH_VAS_READ

Read

Variant Settings for Writing In the variant of the write program, specify the following selection criteria for the value-added service orders: ●

Warehouse Number You can define the physical warehouse within the Warehouse Management system. Only value-added service orders of the selected warehouse are archived.

●

Value-Added Service You can define the value-added service orders to be archived by entering their IDs.

●

Residence Time You can define the length of time that must be exceeded before application data can be archived.

●

Also for Qty Discrepancies If you set this indicator, all value-added service orders which have database status completed with quantity deviations or completed without quantity deviations are archived. If you do not set this indicator, only value-added service orders which have database status completed with quantity deviations are archived.

In the processing options, specify whether EWM is to start the program in test mode or production mode.

SAP Extended Warehouse Management (SAP EWM)

510

1060

SAP Online Help

20.07.2007

For more information about the variant settings, see Variant Maintenance for Archiving Jobs [Extern].

The runtime of the write program depends on the number of value-added service orders to be archived and on the general system performance.

Integration Display Function for Archived Value-Added Service Orders You can use the following field catalog and archive information structures to access archived value-added service orders using the archive information system: ●

Field catalog SAP_WME_VAS

●

Archive information structures SAP_WME_VAS and SAP_WME_VAS_ODM

For more information, see Archive Information System [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

1061

SAP Online Help

20.07.2007

Archiving in Wave Management (SCM-EWM-WAV) Use You can use archiving to remove data records for waves from the database that are no longer required in Wave Management.

Integration The standard data archiving solution is used for archiving in Wave Management. For more information, see Introduction to Data Archiving (CA-ARC) [Seite 1020].

Features Each document category is assigned to an archiving object [Extern] that contains exact information about which data the system is to archive and how. The following table shows the document categories and the relevant archiving objects for Wave Management: 4. Document Category

5. Archiving Object

6. Wave

7. WME_WAVE [Seite 1063]

The archiving objects provide a series of actions that you can use for the data records in the archive administration (transaction SARA).

Activities For more information about the procedure for writing, deleting, and reading data records, see Archiving Procedure [Extern] in data archiving (CA-ARC).

SAP Extended Warehouse Management (SAP EWM)

510

1062

SAP Online Help

20.07.2007

Archiving Waves (SCM-EWM-WAV) Definition You use the archiving object WME_WAVE to archive and delete waves.

Use You can archive waves that Extended Warehouse Management (EWM) saved a certain number of days ago. You can also simultaneously archive waves for multiple warehouse numbers. For test purposes, you can display a list of all the waves to be archived and deleted before archiving them.

Structure Tables EWM uses the archiving object WME_WAVE to archive data from the following tables: Table

Description

/SCWM/WAVEHDR

Wave – Header Information

/SCWM/WAVEITM

Wave Item

Programs The following programs are delivered for the archiving object WME_WAVE: Program

Function

WME_ARCH_WAVE_WRITE

Write

WME_ARCH_WAVE_DELETE

Delete

WME_ARCH_WAVE_READ

Read

Variant Settings for Writing In the variant of the write program, specify the warehouse number and the wave as the selection criteria for the wave. In the processing options, specify whether EWM is to start the program in test mode or production mode. For more information, see Variant Maintenance for Archiving Jobs [Extern].

The runtime of the write program depends on the number of waves to be archived and on the general system performance.

Integration Display Function for Archived Waves You can use the following field catalog and archive information structure to access archived waves using the Archive Information System: ●

Field catalog SAP_WME_WAVE

●

Archive information structure SAP_WME_WAVE

For more information, see Archive Information System [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

1063

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

1064

SAP Online Help

20.07.2007

Archiving in Warehouse Order Processing (SCMEWM-WOP) Use You can use the archiving function to remove data records of the following documents that are no longer required in the system from the database: ●

Telegram flows

●

Relevant resource data

●

Warehouse tasks

●

Warehouse orders

Integration The standard data archiving solution is used for archiving in warehouse order processing. For more information, see Introduction to Data Archiving (CA-ARC) [Seite 1020].

Features Each document category is assigned to an archiving object [Extern] that contains exact information about which data the system is to archive and how. The following table shows the document categories and the relevant archiving objects for warehouse order processing: Document Category

Archiving Object

Telegram Flow

WME_MFS [Seite 1066]

Relevant Resource Data

WME_RSRC [Seite 1068]

Warehouse Task

WME_TO [Seite 1070]

Warehouse Order

WME_WO [Seite 1072]

The archiving objects provide a series of actions that you can use for the data records in archive administration (transaction SARA).

Activities For more information about the procedure for writing, deleting, and reading data records, see Archiving Procedure [Extern] in data archiving (CA-ARC).

SAP Extended Warehouse Management (SAP EWM)

510

1065

SAP Online Help

20.07.2007

Archiving Telegram Flows (SCM-EWM-WOP) Definition You use the archiving object WME_MFS to archive telegram flows.

Use You can archive telegram flows that Extended Warehouse Management (EWM) saved a certain number of days ago. You can also simultaneously archive telegram flows for multiple warehouse numbers. For test purposes, you can display a list of all the telegram flows to be archived and deleted before archiving them.

Structure Tables EWM uses the archiving object WME_MFS to archive data from the following table: Table

Table name

/SCWM/MFSTELELOG

Logging of the Telegram Flow

Programs The following programs are delivered for the archiving object WME_MFS: Programs

Function

WME_ARCH_MFS_WRITE

Write

WME_ARCH_MFS_DELETE

Delete

WME_ARCH_MFS_READ

Read

Variant Settings for Writing In the variant of the write program, specify the Warehouse Number and the programmable logic controller (PLC). You can control conveyor facilities and their components with the PLC. In the processing options, specify whether EWM is to start the program in test mode or production mode. For more information about the variant settings, see Variant Maintenance for Archiving Jobs [Extern].

The runtime of the write program depends on the number of telegram flows to be archived and on the general system performance.

Integration Display Function for Archived Telegram Flows You can use the following field catalog and archive information structure to access archived telegram flows using the archive information system: ●

Field catalog SAP_WME_MFS

●

Archive information structure SAP_WME_MFS

For more information, see Archive Information System [Extern]. SAP Extended Warehouse Management (SAP EWM)

510

1066

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

1067

SAP Online Help

20.07.2007

Archiving Relevant Resource Data (SCM-EWMWOP-RM) Definition You use the archiving object WME_RSRC to archive and delete resource status logs.

Use You can archive resource status logs that Extended Warehouse Management (EWM) saved a certain number of days ago. You can also simultaneously archive resource status logs for multiple warehouse numbers. For test purposes, you can display a list of all the resource status logs to be archived and deleted before archiving them.

Structure Tables EWM uses the archiving object WME_RSRC to archive data from the following tables: Table

Description

/SCWM/USR_ST_LOG

Resource Status Log per User

Programs The following programs are delivered for the archiving object WME_RSRC: Program

Function

WME_ARCH_RSRC_WRITE

Write

WME_ARCH_RSRC_DELETE

Delete

WME_ARCH_RSRC_READ

Read

Variant Settings for Writing In the variant of the write program, specify the warehouse number and the user as the selection criteria for the user status log. In the processing options, specify whether EWM is to start the program in test mode or production mode. For more information, see Variant Maintenance for Archiving Jobs [Extern].

The runtime of the write program depends on the number of resource status logs to be archived and on the general system performance.

Integration Display Function for Archived Resource Status Logs You can use the following field catalog and archive information structure to access archived resource status logs using the Archive Information System: ●

Field catalog SAP_WME_RSRC

●

Archive information structure SAP_WME_RSRC

For more information, see Archive Information System [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

1068

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

1069

SAP Online Help

20.07.2007

Archiving Warehouse Tasks (SCM-EWM-WOP) Definition You use the archiving object WME_TO to archive and delete warehouse tasks.

Use You can archive warehouse tasks that Extended Warehouse Management (EWM) saved a certain number of days ago. You can also simultaneously archive warehouse tasks for multiple warehouse numbers. For test purposes, you can display a list of all the warehouse tasks to be archived and deleted before archiving them.

Structure Tables EWM uses the archiving object WME_TO to archive data from the following tables: Table

Description

/SCWM/ORDIM_CS

Serial Numbers for Confirmed Warehouse Task Item

/SCWM/ORDIM_E

Exception Codes for Warehouse Task

/SCWM/ORDIM_HS

Serial Numbers for HU Item Movements

/SCWM/ORDIM_LS

Serial Numbers for Warehouse Task Log Table

/SCWM/ORDIM_C

Warehouse Tasks Confirmed

/SCWM/ORDIM_H

Warehouse Task: Movements of HU Items

/SCWM/ORDIM_L

Warehouse Tasks Log Table

Programs The following programs are delivered for the archiving object WME_TO: Program

Function

WME_ARCH_TO_WRITE

Write

WME_ARCH_TO_DELETE

Delete

WME_ARCH_TO_READ

Read

Variant Settings for Writing In the variant of the write program, specify the warehouse number and the warehouse task as the selection criteria for the warehouse tasks. In the processing options, specify whether EWM is to start the program in test mode or production mode. For more information, see Variant Maintenance for Archiving Jobs [Extern].

The runtime of the write program depends on the number of warehouse tasks to be archived and on the general system performance.

SAP Extended Warehouse Management (SAP EWM)

510

1070

SAP Online Help

20.07.2007

Integration Display Function for Archived Warehouse Tasks You can use the following field catalog and archive information structure to access archived warehouse tasks using the Archive Information System: ●

Field catalog SAP_WME_TO

●

Archive information structure SAP_WME_TO

For more information, see Archive Information System [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

1071

SAP Online Help

20.07.2007

Archiving Warehouse Orders (SCM-EWM-WOP) Definition You use the archiving object WME_WO to archive and delete warehouse orders.

Use You can archive warehouse orders that Extended Warehouse Management (EWM) saved a certain number of days ago. You can also simultaneously archive warehouse orders for multiple warehouse numbers. For test purposes, you can display a list of all the warehouse orders to be archived and deleted before archiving them.

Structure Tables EWM uses the archiving object WME_WO to archive data from the following tables: Table

Description

/SCWM/WHO

Warehouse Order

Programs The following programs are delivered for the archiving object WME_WO: Program

Function

WME_ARCH_WO_WRITE

Write

WME_ARCH_WO_DELETE

Delete

WME_ARCH_WO_READ

Read

Variant Settings for Writing In the variant of the write program, specify the warehouse number and the warehouse order as the selection criteria for the warehouse order. In the processing options, specify whether EWM is to start the program in test mode or production mode. For more information, see Variant Maintenance for Archiving Jobs [Extern]. You can use the following formula to calculate the necessary space required to archive warehouse orders: length of warehouse order data record x number of warehouse orders. You can determine the data record length in the ABAP Dictionary.

The runtime of the write program depends on the number of warehouse orders to be archived and on the general system performance.

Dependencies Before you can archive warehouse orders using the archiving object WME_WO, you must have archived the relevant warehouse tasks using the archiving object WME_TO [Seite 1070].

SAP Extended Warehouse Management (SAP EWM)

510

1072

SAP Online Help

20.07.2007

Reorganization You can use the program /SCWM/R_REORG_HU_WO_PRINT to delete persistent print data records and Post Processing Framework data records for handling units and warehouse orders that you no longer need in EWM.

SAP Extended Warehouse Management (SAP EWM)

510

1073

SAP Online Help

20.07.2007

Archiving in Labor Management (SCM-EWM-LM) Use You can use archiving to remove data records for documents from the database that are no longer required in Labor Management (LM).

Integration Labor Management uses the central data archiving functions. For more information, see Introduction to Data Archiving (CA-ARC) [Seite 1020].

Features Each document category is assigned to an archiving object [Extern] that contains exact information about which data the system is to archive and how. The following table shows the document categories and the relevant archiving objects for Labor Management: Document Category

Archiving Object

Performance Document

WME_EPD [Seite 1075]

Executed Workload

WME_EWL [Seite 1077]

Indirect Labor Tasks

WME_ILT [Seite 1078]

The archiving objects provide a series of actions that you can use in the archive administration (transaction SARA) for the data records in LM.

Activities For more information about the procedure for writing, deleting, and reading data records, see Archiving Procedure [Extern] in data archiving (CA-ARC).

SAP Extended Warehouse Management (SAP EWM)

510

1074

SAP Online Help

20.07.2007

Archiving Performance Documents (SCM-EWMLM-EP) Definition Archiving object WME_EPD for archiving and deleting performance documents [Extern].

Use You can archive performance documents in Extended Warehouse Management (EWM) whose validity date lies before the date that the system calculates using the current system date minus the number of days that you have specified. You can only archive performance documents with the status Transferred, Deleted, Transferred Manually, or Deleted Manually. For test purposes, you can display a list of all the executed workload records to be archived and deleted before archiving them.

Structure Tables Extended Warehouse Management (EWM) uses the archiving object WME_EPD to archive data from the following table: Table

Description

/SCWM/EPD

Performance Document

Programs The following programs are available for WME_EPD: Program

Function

/SCWM/EPD_ARCH_WRITE

Write

/SCWM/EPD_ARCH_DELETE

Delete

/SCWM/EPD_ARCH_READ

Read

Variant Settings for Writing You can enter the performance document numbers and the name of the HR system as selection criteria. In the processing options, specify whether EWM is to start the program in production mode or test mode. For more information, see Variant Maintenance for Archiving Jobs [Extern].

The runtime of the write program depends on the number of performance documents to be archived and on the general system performance.

Integration Display Function for Archived Performance Documents You can use the following field catalog and archive information structure to access archived performance documents using the Archive Information System [Extern]: ●

Field catalog SAP_WME_EPD

●

Archive information structure SAP_WME_EPD

SAP Extended Warehouse Management (SAP EWM)

510

1075

SAP Online Help

SAP Extended Warehouse Management (SAP EWM)

20.07.2007

510

1076

SAP Online Help

20.07.2007

Archiving Executed Workload (SCM-EWM-LM-WL) Definition Archiving object WME_EWL for archiving and deleting executed workload.

Use You can archive executed workload that Extended Warehouse Management (EWM) saved a certain number of days ago. You can simultaneously archive executed workload for multiple supply chain units. For test purposes, you can display a list of all the executed workload records to be archived and deleted before archiving them.

Structure Tables EWM uses the archiving object WME_EWL to archive data from the following table: Table

Description

/SCWM/EWRKL

Executed Workload

Programs The following programs are delivered for the archiving object WME_EWL: Programs

Function

/SCWM/EWL_ARCH_WRITE

Write

/SCWM/EWL_ARCH_DELETE

Delete

/SCWM/EWL_ARCH_READ

Read

Variant Settings for Writing In the variant of the write program, specify the supply chain unit, the external process steps, the standard activity areas, and the reference object categories as selection criteria for the executed workload. In the processing options, specify whether EWM is to start the program in test mode or production mode. For more information, see Variant Maintenance for Archiving Jobs [Extern].

The runtime of the write program depends on the number of executed workload records to be archived and on the general system performance.

Integration Display Function for Archived Executed Workload Records You can use the following field catalog and archive information structure to access archived executed workload records using the Archive Information System: ●

Field catalog SAP_WME_EWL

●

Archive information structure SAP_WME_EWL

For more information, see Archive Information System [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

1077

SAP Online Help

20.07.2007

Archiving Indirect Labor Tasks (SCM-EWM-LMILT) Definition Archiving object WME_ILT for archiving and deleting indirect labor tasks.

Use You can archive indirect labor tasks that Extended Warehouse Management (EWM) saved a certain number of days ago with the status C (Completed). You can also simultaneously archive indirect labor tasks for multiple warehouse numbers. For test purposes, you can display a list of all the indirect labor tasks to be archived and deleted before archiving them.

Structure Tables Order document management generates the database tables from which data is archived.

Programs The following programs are delivered for the archiving object WME_ILT: Programs

Function

WME_ARCH_ILT_WRITE

Write

WME_ARCH_ILT_DELETE

Delete

WME_ARCH_ILT_READ

Read

Variant Settings for Writing In the variant of the write program, specify the warehouse number and the indirect labor task as the selection criteria for the indirect labor tasks. In the processing options, specify whether EWM is to start the program in test mode or production mode. For more information, see Variant Maintenance for Archiving Jobs [Extern].

The runtime of the write program depends on the number of indirect labor tasks to be archived and on the general system performance.

Integration Display Function for Archived Indirect Labor Tasks You can use the following field catalog and archive information structure to access archived indirect labor tasks using the Archive Information System: ●

Field catalog SAP_WME_ILT

●

Archive information structure SAP_WME_ILT

For more information, see Archive Information System [Extern].

SAP Extended Warehouse Management (SAP EWM)

510

1078