Y36 Scen Overview en De

8/10/2019 Y36 Scen Overview en De

http://slidepdf.com/reader/full/y36-scen-overview-en-de 1/18

Inbound Process with Repacking for Putaway

SAP Extended Warehouse Management (SAP EWM) Rapid-Deployment Solution V2



© 2011 SAP AG. All rights reserved. 2

Step 6 The truck Leaves (SAP EWM)

Physical Activity System Activity

Inbound Process with Repacking for Putaway – Par t 1

Step 1 A truck arrives at thecheckpoint and drivesto the door (SAP EWM)

A truck arrives

The checkpoint clerk notes the TU onthe delivery paper and communicates

the door to the truck driver

The truck drives to the door

The checkpoint clerk creates a TU,assigns the TU to a door, and

confirms the arrival of the truck at thedoor

Step 2Check the delivery noteand assign theinbound deliveries to the TU(SAP EWM)

The GR office clerk assigns theinbound delivery items to the TU

Step 3Unload the truck and check the goods(SAP EWM)

A warehouse worker unloads the truck

A warehouse clerk checks the goodsagainst the delivery note

The warehouse clerk counts thenumber of HUs

Step 4Check goods on thestaging area (SAP EWM)

The warehouse clerk labels the HUs

Step 5 Post the goods receiptand create Wos (SAP EWM)

The truck leaves

The GR office clerk finishesunloading

The warehouse clerk prints HUbarcode labels on external printer and

attach it on the received pallet

The GR office clerk creates thecollective HU (“dummy HU”)

The GR office clerk checks thequantities and posts the goods receipt

The system creates and confirmsWOs to packing station

The GR office clerk confirms thedeparture of the truck




Physical Activity System Activity

Inbound Process with Repacking for Putaway – Par t 2

Step 7 Move the HUs to thepacking station (SAP EWM)

Step 8Repack the goods andcreate putaway WO’s(SAP EWM)

Step 9Put away the goods (SAP EWM)

The system prints HU labels, HUcontent list and creates putaway WOs

to final storage bin

A warehouse worker logs on as aresource

The warehouse worker scans the HUto display the destination storage bin inpacking station

The warehouse worker moves the HUto the packing station

A warehouse worker scans thecollective HU

The warehouse worker identifies thegoods and builds putaway HUs

The warehouse worker builds putawayHUs by repacking the collective HU

The warehouse worker closes theputaway HUs

The warehouse worker labels theputaway HUs

The system determines the open WOfor the putaway HU

A warehouse worker logs on as aresource

The warehouse worker scans aputaway HU

The warehouse worker moves theputaway HU to the final bin

The warehouse worker confirms theWO




Purpose

When the truck arrives, the check-in office creates a transport unit(TU) in SAP EWM and directs the truck to a door. The truck driverhands over the delivery notes to a warehouse clerk, who brings themto the goods receipt office. The GR clerk finds the correspondinginbound deliveries in the system and assigns them to the TU. Afterthe truck is unloaded, the warehouse clerk checks the number ofunloaded pallets at the staging area and the truck can leave. The

warehouse clerk checks the quantities on the pallets and builds asingle handling unit (HU) for each inbound delivery. For this purposehe prints multiple labels with the same HU number on an externalprinter and attaches them to all pallets of one delivery and to thedelivery note. He then takes the delivery note to the GR office. The GRclerk corrects the GR quantities, creates the HU for each delivery andposts the goods receipt. Upon goods receipt, the system

automatically creates and confirms a HU warehouse task to move allpallets of one delivery to a bin located in the inbound section of thepacking station. At the packing station, a packer repacks the goodsonto pallets used for storage. Once a HU is closed, EWMautomatically creates the HU warehouse task for the putaway of thepallet to the final bin. A forklift driver executes the putaway with thehelp of a mobile device.




Prerequisites

• You have integrated SAP EWM with SAP ERP

• You have configured the warehouse structure and master data

• You have configured your systems for this process

•Vendors participating in this process send ASNs. The ASNs exist asinbound deliveries in SAP ERP and SAP EWM




Process step 1:

A truck arrives at the checkpoint and drives to the door (SAP EWM)

The checkpoint clerk creates a TU. He writes the TU number on one ofthe delivery notes. As the goods delivered regularly by the vendor arealways unloaded at the same doors, the checkpoint clerk checks ifone of those doors is free. If yes, he assigns a door to the TU anddirects the truck to the assigned door. Assuming a small to mediumsize yard the checkpoint clerk confirms the arrival of the truck at thedoor. This step is necessary for the checkpoint clerk to see that the

door is occupied. If no door is free yet, the truck driver must wait. Thecheckpoint clerk informs the truck driver as soon as a door is freeand assigns then the TU to the door.

For large yards it would be possible to have the arrival at the door

confirmed by the GR office in a separate step. In this case thecheckpoint clerk only confirms the arrival of the truck at thecheckpoint.


http://slidepdf.com/reader/full/y36-scen-overview-en-de 7/18© 2011 SAP AG. All rights reserved. 7

Process step 2:Check the delivery notes and assign the inbound deliveries to the TU (SAP EWM)

The truck driver brings the delivery notes to the goods receipt office.

The GR office clerk finds the corresponding inbound deliveries in thesystem and assigns them to the TU.

Note: If an inbound delivery does not exist yet due to acommunication failure of the ASN, the GR office clerk creates the

inbound delivery manually with the external delivery note number. Ifthe ASN communication failure is solved after manual creation of theinbound delivery, the system will issue an error upon ASN receptionand no duplicate will be created.



Process step 3:Unload the truck and check the goods (SAP EWM)

The unloading can carried out at the same time as the previous step.

A forklift driver unloads the truck. When the warehouse clerk comesback from the GR office, he counts the number of unloaded palletsper delivery. He or she writes it on the delivery note then hands overthe delivery notes to the truck driver, who takes the revised deliverynote to the GR office.

Note: The activities above are not carried out in the system.

The GR office clerk confirms the unloading.



Process step 4:

Check goods on the staging area

In this process, this step is not realized in the system.

For each inbound delivery, the warehouse clerk working at thestaging area prints on an external printer as many HU barcode labelsas the number of pallets plus one label to be used by the GR clerk forthe creation of the HU in the system. All HU barcode labels of onedelivery have the same HU number (needed for moving the physical

HUs of one delivery to the packing station).The warehouse clerk checks the goods against the delivery note,attaches the HU barcode label on each pallet and takes the deliverynotes with annotations and the additional HU label to the GR office.

In case of quantity differences, you write annotations on the delivery

note.



Process step 5:Post the goods receipt and create WOs (SAP EWM)

The GR office clerk adapts the inbound deliveries according to the

annotations on the delivery notes. In case of a quantity deviation or a missingproduct, the GR office clerk adjusts the quantity in the system with anappropriate process code. In case an additional product has been delivered, theGR office clerk creates a new inbound delivery item for the additional product.

The GR office clerk creates the HUs with unknown content (“dummy”HU) for each inbound delivery using the external HU number according to thelabel printed on the external barcode printed in the staging area.

Finally the GR office clerk posts the goods receipt for the TU. Thesystem communicates the goods receipt to SAP ERP. When the GR is posted,the system automatically creates the HU-WTs and warehouse orders (WOs) tomove the goods to the next empty bin of the inbound section of the packingstation. All pallets of one TU will be moved to the same bin. If the WOs cannotbe created because all inbound bins of the packing station are occupied, the

system regularly re-tries to create the WOs automatically.



Process step 6:

The truck leaves (SAP EWM)

The truck leaves the door and the premises. The GR office clerk confirms thedeparture of the truck from the checkpoint and from the door. This step isnecessary for the checkpoint clerk to see in the system that the door is free.

In large yards, the checkpoint clerk can confirm the departure from thecheckpoint separately. In this case, the GR office clerk only confirms thedeparture of the truck from the door.



Process step 7:

Move the HUs to the packing station (SAP EWM)

In this step a warehouse worker moves the HUs to the packingstation. This step is executed using a mobile device.

When the warehouse clerk comes back from the GR office, he signalsa forklift driver to start removing the pallets from the staging area.

The forklift driver picks the first pallet from the staging area andscans the HU label of the pallet with his mobile device. Thedestination bin in the inbound section of the packing station appearson the display. He drops the pallet on that bin. He proceeds the sameway with all pallets from the staging area.

A peculiarity of this process is that the system creates one HU WT forall pallets of the delivery and confirms it before the pallets are

physically moved to the packing station. As a consequence the HU isalready located at the packing station in the system. The forklift driverexecuting the physical move queries the current location of the HU inthe system in order to know where he has to bring each pallet to.



Process step 8- Part 1:Repack the goods and create putaway warehouse orders(SAP EWM)

The inbound section of the packing station is divided into severalbins. Each bin is equipped with a card holder. One packer inserts hiscard into the card holder of one bin to signal that he is working onthat bin. He picks up the first pallet from that bin and scans its HUlabel. The HU is displayed automatically by the system. He navigatesto the HU content, picks a product from the HU and selects thecorresponding HU item in the system. The system displays the total

quantity of the delivery item and proposes a packaging material and atarget quantity for the product. The packer adjusts the item quantity ifnecessary and repacks the product onto the new HU. The HU iscreated in the system upon confirmation of this step. Upon HUcreation a HU label is printed automatically. The packer attaches theHU label to the HU. If he has packed exactly the target quantity ontothe HU, he closes the HU immediately in the system.The systemprints automatically a HU content list. The packer attaches the HUcontent list to the HU and moves it physically to the outbound sectionof the packing station. EWM automatically creates a HU warehousetask for the putaway to the final storage type. He proceeds the sameway with all pallets from the source bin.



Process step 8- Part 2:Repack the goods and create putaway warehouse orders(SAP EWM)

Once all products have been repacked, he or she closes all remaining

HUs in the system, attaches the HU content list to the correspondingHU and moves the HUs physically to the outbound section of thepacking station. EWM automatically creates the HU warehouse tasksfor the putaway to the final storage type.

At regular time intervals empty pallets used for storage are brought tothe packing station and the empty pallets from the vendors areremoved. These steps are not realized in the system.

If the system cannot propose packaging information for a productdue to missing packaging specification, the packer informs awarehouse clerk, who will identify the product and create thepackaging specification. In the meantime the packer can re-pack the

other products. Once all other products have been repacked, only theproduct with missing packaging specification remains on the sourceHU. The packer puts the pallet aside. In the system the HU Is movedfrom the inbound section to the main section, so that the inboundsection is free for the next delivery. Once the warehouse has createdthe packaging specification, the packer can re-pack the product andtrigger the final putaway.



Process step 9:

Putaway the goods (SAP EWM)

In this step the warehouse worker moves the putaway HUs to the final

bins. This step is executed using a mobile device .

A warehouse worker (for example, a forklift driver) takes theequipment necessary (for example, vehicle, mobile device) and logson as a resource. The warehouse worker picks one HU from theoutbound section of the packing station and scans its ID. The systemfinds the open HU-WT. The worker is prompted to bring the HU to thefinal destination bin in the pallet storage. There he drops the HU andscans the bin, thus confirming the WT. He drives back to the packingstation to proceed with the next HU.

If the warehouse worker finds an empty pallet on the destination bin,he removes it from the bin and brings it to the area reserved forempty pallets. This step is not realized in the system.



Process Monitoring

Process Step Objects To Be Monitored Activities

All GR workload list On the SAP Easy Access screen, choose ExtendedWarehouse Management -> Monitoring -> GoodsReceipt Workload .

1 Assigned/Free doors On the SAP Easy Access screen, choose ExtendedWarehouse Management -> Shipping and Receiving ->Maintain Door Assignment .

2 and 5 TU On the SAP Easy Access screen, choose ExtendedWarehouse Management -> Monitoring -> WarehouseManagement Monitor -> Inbound -> Documents ->Receiving Overview -> Transport Unit Overview Inbou. -> Transport Unit Header Inbound .

4 Open deliveries in terms of GR On the SAP Easy Access screen, choose ExtendedWarehouse Management -> Monitoring -> WarehouseManagement Monitor -> Inbound -> Documents ->Inbound Delivery .

Select inbound deliveries by delivery date and goodsreceipt status.

7 and 9 Open deliveries in terms ofwarehouse activity (WT not createdyet, WT not confirmed yet)

On the SAP Easy Access screen, choose ExtendedWarehouse Management -> Monitoring -> WarehouseManagement Monitor -> Inbound -> Documents ->Inbound Delivery .

Select inbound deliveries by delivery date and putawaystatus or planned putaway status.

9 Open putaway WOs for thedestination activity areas

On the SAP Easy Access screen, choose ExtendedWarehouse Management -> Monitoring -> WarehouseManagement Monitor -> Documents -> WarehouseOrder .

Select WOs by state and activity area.



More Information

For more information, see SAP Library for SAPExtended Warehouse Management on the SAP HelpPortal at http://help.sap.com .

http://help.sap.com/

http://help.sap.com/



© 2011 SAP AG All rights reserved 18

No part of this publication may be reproduced or transmitted in any form or for any purposewithout the express permission of SAP AG. The information contained herein may bechanged without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietarysoftware components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of MicrosoftCorporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registeredtrademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks orregistered trademarks of Adobe Systems Incorporated in the United States and/or othercountries.

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 aretrademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, WorldWide 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 fortechnology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,StreamWork, and other SAP products and services mentioned herein as well as t heirrespective logos are trademarks or registered trademarks of SAP AG in Germany and othercountries.

© 2011 SAP AG. All rights reserved

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, CrystalDecisions, Web Intelligence, Xcelsius, and other Business Objects products and servicesmentioned herein as well as their respective logos are trademarks or registered trademarksof Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybaseproducts and services mentioned herein as well as their respective logos are trademarks orregistered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respectivecompanies. Data contained in this document serves informational purposes only. Nationalproduct specifications may vary.

The information in this document is proprietary to SAP. No part of this document may bereproduced, copied, or transmitted in any form or for any purpose without the express priorwritten permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or anyother agreement with SAP. This document contains only intended strategies, developments,and functionalities of the SAP® product and is not intended to be binding upon SAP to anyparticular course of business, product strategy, and/or development. Please note that thisdocument is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does notwarrant the accuracy or completeness of the information, text, graphics, links, or other itemscontained within this material. This document is provided without a warranty of any kind,either express or implied, including but not limited to the implied warranties ofmerchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct,

special, indirect, or consequential damages that may result from the use of these materials.This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has nocontrol over the information that you may access through the use of hot links contained inthese materials and does not endorse your use of third -party Web pages nor provide anywarranty whatsoever relating to third-party Web pages.

Y36 Scen Overview en De

Documents

Transcript of Y36 Scen Overview en De