Professional Documents
Culture Documents
Empowering The Warehouse Worker PDF
Empowering The Warehouse Worker PDF
2
What We’ll Cover
Wrap-up
3
Why the Need for Empowerment?
?
international competition from countries with low labor cost
• This leads to demands for cost effective operations
– Higher degree of process automation
– Better utilization of FTE resources
– Working smarter – Rather than harder
• Through RF empowerment, you allow your warehouse workers to
supply your warehouse operations with intelligence and execution
power
4
The Power of Worker Empowerment
Provide the warehouse workers with tools and systems for utilizing
their warehouse knowhow in order to maintain and improve effective
warehouse operations
• Move execution of complete SAP processes from PC screens to
the warehouse floor
• Correct errors immediately when discovered – at the warehouse
floor
• Perform process adjustments during execution to utilize worker
know-how
• Utilize the power of real-time data updates
• Supply your operation with agility, flexibility, and efficiency
5
Mobile Equipment Is the Key
Wifi Antenna
Barcode Scanner
Display
Keyboard
6
SAP Mobile
7
“Static” WM Is Simply Too Inflexible
The transfer order (moving goods in the warehouse) is a static object when executed without RF equipment
Deviations?
Go to terminal to
correct.
8
The Advantages of Using Mobile Warehouse Equipment
9
What We’ll Cover
Wrap-up
10
The Technical Enablers …
11
All Warehouse Movements Can Be Carried
Out with RF
• Put-away of P.O.
• Staging to Production
• Put-away from Production
• Replenishment of pick-bin
• Picking of Delivery
12
Using the Mobile Menu, Performing Tasks
13
RF Empowerment in SAP ECC
14
Empower Your Warehouse Workers by
Letting Them Influence the Work Execution from the RF Terminal
15
Registering Differences in TO Execution
Note: Correcting larger stock level errors can take several iterations this way!
16
Empower Your Warehouse Workers by
Letting Them Perform Complete Processes from RF Terminals
17
Complete Goods Receipt from the Warehouse
Floor Using Inbound Deliveries
To
GR
To GR
18
Performing Goods Receipt Using RF Equipment
19
Performing Goods Receipt Using RF Equipment (cont.)
20
The Delivery Is Completely Processed on RF Terminal
21
The Delivery Is Completely Processed on RF Terminal (cont.)
22
Registering Differences During Actual Put Away
23
Goods Receipt Posted on the RF Device (After Put Away)
And the
received
quantity can
be automati-
cally updated
back into
the del.
24
Advantages of RF with Inbound Deliveries
• All processes related to the Goods Receipt are carried out on the RF device
(no need to access an office terminal)
• Any differences discovered during put away are registered in real-time
• Actual GR posting does not take place until after put away
• GR done on the actually received quantities
25
Further Standard Empowerment – Allow Users to Perform Ad Hoc
Physical Counting
26
A Great Use of RF Execution in Standard SAP ERP
• Utilize the RF availability during picking to spread out your Inventory count effort with “Zero Stock Check”
27
What We’ll Cover
Wrap-up
28
Extend Standard SAP with Missing RF Transactions
• Why SAP standard is not enough for most
warehouses
– Ad hoc warehouse movements
– Blocking/unblocking of bin, products, or
pallet 1. Inbound Proc. >
– Maintenance of master data by RF
– GI to production/Cost Center/Project, etc. 2. Outbound Proc. >
– GR of purchase orders (without Inbound
delivery) 3. Ad Hoc Move > Don’t be afraid of
– ID and re-print pallet labels extending standard SAP
with your own RF
– Adding additional process checks 4. Inquiries > transactions
• Missing transactions are programmed in
ABAP, added to the RF menu, and
translated into HTML 5. Master Data >
29
Example of a Developed Transaction – Ad Hoc Movement
30
Other Examples of RF Transactions Created
in Previous Projects
• Reprint pallet labels
– ID the pallet by scanning the bin and selecting from a list or by scanning the non-missing labels
• Change picking strategy, put-away strategy, or palletization data of a material from terminal
– ID product by scanning product EAN label, SAP product number, or by scanning pallet or bin number
• Let the user overview picking queues (and number of open TOs)
– Select queue and TO to execute from list instead of “system guided”
• Post Goods Issue to production
– Scanning: Product number, Batch number, or the Storage Unit
• Various checks: Batch to delivery, Product to HU and more.
31
What We’ll Cover
Wrap-up
32
EWM – Built for RF Execution
• ERP WM – Built for one step (static) movements
• EWM – Built for multiple step (dynamic) movements
DC
33
Comparing RF Functionality – EWM vs. ERP WM
34
Standard RF Framework in EWM
• RF framework looks similar to the ERP framework
– Conceptual addition of “Resources”
– Possibility added to perform flexible screen design
– New standard functionality for data lookup during execution
• New standard Ad Hoc transactions added
– Move HU or material
• New concept for handling deviations introduced
– Confirmation correction
– Deviation handling through exception codes
35
EWM Ad Hoc Transaction
• Ad hoc movements
have been added to
the standard RF
portfolio in SAP EWM
• Move both HUs or
products
• In addition, tasks and
stock queries of HUs,
products, and bins
are available during
most RF movements
36
Get in Control of Process Deviations in EWM
with Exception Codes
• With EWM, “Process Exceptions” enter the RF environment through 4 letter exception codes
• Exception Codes are configured in the system and are a way for the warehouse worker to register process
deviations
• Based on the exception codes, the system can perform a number of follow-up tasks
– Create/change the warehouse task(s)
– Change status for the bin or the Handling Unit
– Change the quantities of the referencing delivery document (e.g., reduce delivered quantity)
– Start additional processes through SAP Workflow (replenishment, mail notification, etc.)
– Notify warehouse supervisors by raising warehouse alerts
37
Exception Codes Are Entered During RF
Execution to Register Deviations
A process deviation process is started by entering a 4 letter Exception Code
Enter “LIST” in the Exception Code field to get a list of all relevant Exception
Codes for the current process step
38
Example – Splitting Pick-Task to Multiple
Pallets
39
Example – Splitting Pick-Task to Multiple
Pallets (cont.)
If warehouse worker cannot remember the process code to use, he can get
them displayed in a selection list
40
Example – Splitting Pick-Task to Multiple
Pallets (cont.)
41
Example – Splitting Pick-Task to Multiple
Pallets (cont.)
User wants to create a new pick HU, enters User enters packaging material “PALLET”
Exception code CHHU and has a new HU created
The remaining quantity has automatically been moved to another task that is
automatically processed
42
Example – Splitting Pick-Task to Multiple
Pallets (cont.)
All process deviations were carried out
without leaving the picking process
A new HU is created as part of the picking process and the task is confirmed
43
Confirmation Correction with RF
With “Confirmation Correction,” you can even change processes that have already been confirmed from the
mobile equipment!
44
What Is Achieved with Exception Codes and Confirmation Correction?
45
Other Advanced Utilization of RF Execution in EWM
46
Utilize RF – Cross-Docking, Making Put-Away
Process More Effective
The standard put-away and picking process
1. GR posted, stock enters
GR GI warehouse
2. Stock put-away, available for
picking
3. A new picking task can pick
from the stock
47
Utilize RF – Interleaving Pick and Put Away
Reduce deadheading by defining a “Queue Execution Sequence” for Task Interleaving
GI
48
Utilize RF – Resource Execution Constraints
Avoid waiting time by limiting the resource access to warehouse zones
49
Alternatives to Normal RF Execution Are
“Hands Free”
50
What the Future Might Have in Store
• Google Glass (and similar devices) is on its way to the warehouse
• Provides a heads up display in glasses – A wearable data screen
• SAP & Vuzix bring you augmented reality solutions
51
What the Future Might Have in Store (cont.)
52
What the Future Might Have in Store (cont.)
53
What We’ll Cover
Wrap-up
54
What We’ll Cover
Wrap-up
55
Where to Find More Information
• http://help.sap.com/SCENARIOS_BUS2012/helpdata/EN/71/5f4296318f4493a815eebce7c0e7a6/frameset.htm
– Description and examples of Exception Handling
• http://en.sap.info/sap-goes-wearable/9444
– Video of Augmented Reality Solutions for the Enterprise by SAP & Vuzix
• www.supplychain247.com
– Survey on U.S. Warehouse Operations, October 2013
• http://help.sap.com/saphelp_scm70/helpdata/EN/f8/09302b46504a15980f2f5d713b3fd8/content.htm
– Information about SAP NetWeaver BI in SAP EWM
56
Your Turn!
57
Disclaimer
SAP, R/3, mySAP, mySAP.com, SAP NetWeaver®, Duet®, PartnerEdge, 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. Wellesley Information Services is neither owned nor controlled by SAP.
58