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:

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. See: Defining Transaction Reasons.

Note: Reason codes and their related corrective action workflows are created during system set up. For more information about corrective actions, see the Oracle Workflow User's Guide.

Transactions reasons also have an associated reason context. Transaction reasons and the associated contexts are required when you enter an exception. The available reason contexts are as follows:

Note: Use the Pick Load Page Setup window to enable over picking and under picking. See Explaining Pick Load Setup and Explaining Over Picking.