Shipping Goods from the Warehouse

Configuring Exception Handling

Objective

After completing this lesson, you will be able to handle exceptions and picking differences.

Exceptions

In the everyday operation of the warehouse things can go wrong, for example, a picker cannot find all of the materials they need to pick in a bin; a scanner which is part of the MFS cannot read an HU label; a bin that is supposed to be empty is not; when putting away a pallet, less material is on the pallet than there should be.

Whenever an exceptional situation arises in the warehouse, an exception code is needed to describe in the system what the reason or cause for the exception is, and to trigger the action. Such an action can be highly automated (for example, a delivery can be changed or a physical inventory document created), or very basic (someone is informed that the exceptional situation occurred).

Image shows a worker checking stock in a warehouse and an illustration of a checklist for exception code handling

Examples of Exception Codes

SAP delivers several exception codes for all kinds of warehouse situations. The following are examples of exception code situations:

BIDP, Partial Pick Denial:
The user cannot find the required quantity in the bin. When entering the exception in the mobile device, the system brings up a screen where the user has to confirm the quantity they can pick. The system then tries to trigger a new warehouse task to pick the missing quantity from another bin. Additionally, you can set up the system to:
  • Trigger a workflow so someone is informed about the situation
  • Create a physical inventory document
  • Block the bin for putaway and picking
BIDF, Full Pick Denial:
The user cannot access the bin where they need to pick from. This exception is entered in the mobile device. The system can create a new warehouse task to pick from a different bin. Additionally, you can set up the system to trigger a workflow so someone is informed about the situation; that a physical inventory document is created; and that the bin is blocked for putaway and picking.
DIFD, Difference as Charges for Inbound Delivery:
During putaway the material in the final bin is counted and a difference is found. The full quantity was not delivered from the vendor. The exception is raised, the quantity in the inbound delivery is adjusted, and the goods receipt is corrected.
DIFW, Difference as Charges for Warehouse:
During putaway a piece falls from the pallet and is broken. The correct quantity was delivered, but in the end there is less than delivered. The difference is posted to the Difference Account.
MCAP, Capacity Bottleneck:
An MFS resource, a conveyor segment, or a communication point is full and cannot take any more tasks. However, by triggering the exception code, the system knows that no further warehouse tasks can be sent to the element until the exception is solved. Such an exception is triggered through an internal exception code.

Internal Exception Codes:

The system can trigger internal exception codes. These are assigned to external exception codes, which are codes that can also be entered manually. The internal exception code does not offer settings for the follow-up actions — this is set up in the external exception code.

An example is pick denial. A pick denial can be entered by a warehouse worker when a bin is not accessible or the required quantity is not available. In this case, the worker has to enter the correct exception code. The system can also trigger a pick denial. When creating a warehouse task in the background, but the required quantity cannot be found by the system in the warehouse, the system can trigger a internal pick denial exception code. This triggers the connected external exception code and the assigned follow-on action is started.

Summary

  • Exception codes are triggered whenever an exceptional situation arises in the warehouse — whether caused by a warehouse employee, a sensor, or the system — and are always assigned to a business context and an execution step to describe the reason and initiate the appropriate action.
  • Follow-on actions assigned to exception codes include internal process codes (such as finding a new bin or triggering replenishment), workflow triggers, status management (blocking a bin or HU), and alerts in the Alert Monitor.
  • SAP delivers predefined exception codes for common warehouse scenarios — such as partial or full pick denial, delivery differences, and MFS capacity bottlenecks — and also supports internal exception codes that the system can trigger automatically to initiate the connected external exception code and its follow-on actions.

Set Up Pick Denial Processing