Exceptions 
The list of valid exceptions depends on the type of warehouse task (HU warehouse task or product warehouse task) and on the current step of the process (source storage bin or destination storage bin).
Features
The following exception steps are available for pick by voice:
P1: PbV HU WT Action on Source Data
P2: PbV HU WT Action on Target Data
P3: PbV Product WT Action on Source Data
P4: PbV Product WT Action on Target Data
The following exceptions are supported in the business contexts TIM — Confirm Warehouse Task (Intern. Movemnt) and TPI — Confirm Warehouse Task (Stock Removal):
HU warehouse task on source storage bin (Step P1)
DIFF — Post with Difference
HUMI — No Handling Unit Exists
NEXT — Continue
SKVA — Skip Complete Validation
HU warehouse task on destination storage bin (Step P2)
CHBD — Change Destin. Storage Bin (Location)
DIFF — Post with Difference
SKVA — Skip Complete Validation
Product warehouse task on source storage bin (Step P3)
DIFF — Post with Difference
NEXT — Continue
SKVA — Skip Complete Validation
SPLT — WT Split
Product warehouse task on destination storage bin (Step P4)
CHBD — Change Destin. Storage Bin (Location)
DIFF — Post with Difference
SKVA — Skip Complete Validation
SPLT — WT Split
The following internal exceptions allow you to directly trigger exceptions with pushbuttons from the main pick by voice screen:
BIDF — Trigger Pick Denial for Entire Quantity
BIDP — Trigger Pick Denial for Partial Quantity
DIFF — Trigger default difference
LIST — Trigger List of Valid Exceptions
The following internal exceptions support error handling in RF warehouse task confirmation:
RF01 — Error during WT confirmation in RF
RF02 — Error during WT creation in RF
For all the internal exceptions, you must define exceptions for execution step Data Verification in Background. You do this in Customizing for Extended Warehouse Management under 
Cross-Process Settings
Exception Handling Define Exception Codes 
.
The exception NEXT only works for the same step. This means that at the end of the WT list for the source step, it is not automatically changed to the destination step. The system speaks the message “End of task list. Next task not possible” to the user.
The internal exceptions BIDF and BIDP are dependent on the quantity the user has entered before the pushbutton or command Pick Denial is triggered. If the quantity field is empty, the system assumes there is a full pick denial and triggers the internal exception BIDF. If the quantity field is not empty, the system assumes there is a partial pick denial and triggers the internal exception BIDP.
The pushbutton Difference on the source screen for product warehouse tasks is linked to the internal exception DIFF. You can maintain a default difference exception code, based on the internal exception, which decides the type of difference, for example, difference as charges for the warehouse or difference as charges for the storage bin. This exception code is determined by choosing Difference. The quantity entered is the available quantity, and the difference quantity is calculated from the requested quantity minus the entered quantity. You can use this to trigger difference reporting easily without navigating to the exception code list screen.