Error Handling 
If errors occur during warehouse task (WT) confirmation, the system sends the pick-HU to a dedicated clarification bin so that the error can be analyzed and resolved. The picker can follow the guidance of the pick by voice system. You can specify a clarification bin for each activity area and
activity on the SAP Easy Access screen under 
Extended Warehouse Management 
Master Data Storage Bin Assign Start/End Storage Bin for Activity Area
or by entering the transaction code /SCWM/SEBA.
The following error scenarios are possible:
The confirmation of the pick WT from the source bin to the destination bin fails.
This can happen if, for example, the Customizing settings for the storage type allow the available quantity to be a negative value. Thus a WT can be created with a quantity which exceeds the quantity actually available in the bin. However, the WT cannot be confirmed during picking if the available quantity on the bin has not increased. The pick WT stays open but is no longer assigned to a picker for processing, and the pick HU is sent to the clarification bin. If a pick-HU WT to the original destination already exists, it is canceled and a new one to the clarification bin is created.
The asynchronous creation of the pick-HU warehouse task fails.
This can happen if, for example, the destination bin of the pick-HU is blocked. In this case the RFC queue contains an entry for the HU which cannot be processed. The system creates a WT with the clarification bin as its destination, and deletes the entry from the queue. WTs to the clarification bin are always created synchronously, to ensure stable error handling.
NoteThe clarification bin should not be located in a a storage type with the role staging area. If it is, the staging area of the outbound delivery item referenced by the WT is set to the clarification bin. This is done because the delivery is updated with the current WT data during WT confirmation.
End of the note.
If the WT confirmation aborts with an error, the system moves the pick-HU to the clarification storage bin for further processing. The WT is marked internally as faulty, and stays open but is not assigned to a picker for processing any more.
Warehouse Order Split
If a picker leaves the picking transaction while some WTs of the processed warehouse order (WO) are still open, he can send the remaining WTs back to the queue so a different picker can process them. The WO is then split, so the open WTs are moved to a new WO. This also happens if you delete the assignment of a WO to a resource in the warehouse management monitor.
WTs that are still open due to an error remain in the original WO, as they have already been processed. This means that the erroneous WTs remain assigned to the picker that actually processed them.
Exception Codes
If an error occurs during WT confirmation, an internal exception code is raised. The following internal exception codes are available for pick by voice:
RF01 - Error during WT confirmation in RF
This exception code is raised if the confirmation of a pick WT from the source bin to the resource fails.
RF02 - Error during WT creation in RF
This exception code is raised if the confirmation of the pick-HU WT from the resource to the destination bin fails.
By assigning an exception code to the internal exception code, an alert can be triggered in order to inform the worker responsible for checking the HUs on the clarification bin. The exception code must be valid for the business context TPI – Confirm Warehouse Task (Stock Removal) with the execution step A0 – Data Verification in Background which is used for exceptions triggered by the system.
There is a warehouse management monitor node available to display the alerts. In the standard SAP monitor it is located under Alert Exception . From this node you can also navigate to the faulty WO
using the monitor method Display WO of WT. Here you can confirm WTs that were left open due to errors after the problem is solved. In order for your exception to be displayed in this monitor node, you must activate the option With History for
your exception code.
Clearing Errors
When a pick-HU is rerouted to the clarification bin, you have to check the HU, confirm any pick WTs that are still open, and forward the HU to its original destination.
When you are informed by an alert that a HU is being sent to the clarification bin, you must first use the monitor node Alert Exception to identify the erroneous warehouse order. You can check here whether some of the pick WTs are still open. If multiple pick-HUs were sent to the clarification bin, you first have to check which one the product of the WT was picked into. As the remaining WTs could not be confirmed, they still point to the original destination and not to the pick-HU. When you have matched the WTs that are still open with the correct HUs, confirm the WTs in the foreground and change their destination to the appropriate pick-HU.
After you finish processing a HU in the clarification bin, you must create an ad-hoc WT to the HU's original destination. You can do this with the transaction Move Handling Unit (/SCWM/ADHU) which you can find on the SAP
Easy Access screen under Extended Warehouse Management Work Scheduling Create Warehouse Task Without Reference .