Explaining Task Unloading
A task that has been loaded can be unloaded at any point prior to the task drop.
Unloading a task enables you to reverse the task load, returning the material, or full LPN, to the same locator from which it was picked. If the material requirement that has created that task has been cancelled, then the task will be cancelled when it is unloaded.

This is particularly for change management of sales orders and work orders.

You can use the Manual Unload page to unload tasks loaded using advanced pick load.

To unload a task:
1. Navigate to the Manual Unload page.
2. Enter the task to unload in the Current Task field.
3. Choose <Unload> to unload the task, or <Cancel> to cancel the task unload.
4. If you choose <Unload>the Unload page appears. The unload page displays the From LPN, From Subinventory, From Locator, Item, UOM and Qty, or displays the Subinventory and Locator information if you are unloading the entire LPN.
5. Choose <Unload> to unload the task, or choose <Cancel> to cancel the unload.

Explaining Task Skipping
An operator may be unable to perform a task that has been dispatched to them due to conditions outside their control, and do not warrant another type of task exception. For example, the aisle to which he or she was directed may be temporarily blocked. The operator may skip the task it is returned to the pool of pending tasks and dispatched again.

Task Exceptions
If at any point during the pick process the user reports a discrepancy, warehouse manage can initiate a corrective action workflow. Discrepancies might include any of the following:

• Picking a different quantity than the quantity suggested by the system
• Dropping material into a different staging lane than the staging lane suggested by the system. If a discrepancy is reported, the system immediately directs the user to an audit screen, where he or she is prompted to indicate a reason for the mismatch.

Each reason has an associated corrective action workflow, which will be initiated immediately after an exception occurs. For example, a corrective action workflow might notify the warehouse supervisor, through pager, mail, or other alert mechanism, that an exception has occurred. Corrective actions can also notify customer service that a
potential backordered situation exists on a sales order.

Corrective actions can also place a location on hold so that subsequent material allocations do not source material from that locator. These actions can also request a cycle count for a particular locator, or re-release the balance of the sales order line so that it can be sourced from another location.

When you enter an exception during the picking process, you can enter a reason for the exception. You setup the exception reasons in Oracle inventory.