Show TOC

Function documentationError Handling

 

If errors occur during warehouse task confirmation, the assumption is that most errors, which are not already shown as part of verification, cannot be resolved by the picker. Therefore the system sends the pick-handling unit (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 Start of the navigation path Extended Warehouse Management Next navigation step Master Data Next navigation step Storage Bin Next navigation step Assign Start/End Storage Bin for Activity Area End of the navigation path or by entering the transaction code /SCWM/SEBA. If you do not specify a clarification bin, the system displays error messages instead. Note that this situation does not relate to errors the picker must be notified about, such as verification errors. Therefore if, for example, the picker scans the wrong source bin, an error is still shown to the picker and he or she has to correct the error.

The following error scenarios are possible:

  • The confirmation of the pick warehouse task from the source bin to the destination bin fails.

    This error scenario can happen if, for example, the Customizing settings for the storage type allow the available quantity to be a negative value. Thus a warehouse task can be created with a quantity which exceeds the quantity actually available in the bin. However, if the available quantity on the bin has not increased, the warehouse task cannot be confirmed during picking. The pick warehouse task 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 warehouse task 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 error scenario can happen if, for example, the destination bin of the pick-HU is blocked. In this case, the Remote Function Call (RFC) queue contains an entry for the HU that cannot be processed. The system creates a warehouse task with the clarification bin as its destination, and deletes the entry from the queue. The system always creates warehouse tasks to the clarification bin synchronously, to ensure stable error handling.

    Note Note

    If a clarification bin is maintained and an error occurs, the picker is directed to the clarification bin. This situation can happen for different kinds of errors. The assumption is that these errors should be checked by a supervisor at the clarification bin. However, this situation could include errors the picker might resolve himself or herself. But still he or she is directed to the clarification bin. The errors can be, for example:

    • A batch-neutral warehouse task is confirmed by the picker with a batch that physically has enough stock. However according to the system, there is not enough stock.

    • The picker picks the goods of too many warehouse tasks into the same pick-HU and exceeds the capacity of the pick-HU.

    • The source storage bin or destination storage bin is locked by another user.

    The clarification bin should not be located in a storage type with the staging area role. If it is, the staging area of the outbound delivery item referenced by the warehouse task is set to the clarification bin. The staging area is set to the clarification bin because the delivery is updated with the current warehouse task data during warehouse task confirmation.

    End of the note.

If the warehouse task confirmation aborts with an error, the system moves the pick-HU to the clarification bin for further processing. The warehouse task is marked internally as faulty, and stays open but is not assigned to a picker for processing any more.

Prerequisites

If you want to influence error handling using clarification bins during RF picking, you must implement the Restriction of Clarification Bin (/SCWM/EX_RF_PICK_CLF_BIN) Business Add-In in Customizing for Extended Warehouse Management under Start of the navigation path Business Add-Ins (BAdIs) for Extended Warehouse Management Next navigation step Mobile Data Entry Next navigation step Picking with Radio Frequency (RF) End of the navigation path.

Features

Warehouse Order Split

If a picker leaves the picking transaction while some warehouse tasks of the processed warehouse order are still open, he or she can send the remaining warehouse tasks back to the queue so a different picker can process them. The system then splits the warehouse order so the open warehouse tasks are moved to a new warehouse order. This situation also happens if you delete the assignment of a warehouse order to a resource in the warehouse management monitor.

Warehouse tasks that are still open due to an error remain in the original warehouse order, as they have already been processed. This means that the erroneous warehouse tasks remain assigned to the picker that actually processed them.

Exception Codes

If an error occurs during warehouse task 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

    The system displays this exception code if the confirmation of a pick warehouse task from the source bin to the resource fails.

  • RF02 - Error during WT creation in RF

    The system displays this exception code if the confirmation of the pick-HU warehouse task from the resource to the destination bin fails.

For all the internal exceptions, define exceptions for the execution step Data Verification in Background in Customizing for Extended Warehouse Management under Start of the navigation path Cross-Process Settings Next navigation step Exception Handling Next navigation step Define Exception Codes End of the navigation path.

By assigning an exception code to the internal exception code, an exception can be triggered 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) and TIM - Confirm Warehouse Task (Intern. Movemnt) with the execution step A0 – Data Verification in Background, which is used for exceptions triggered by the system.

In the warehouse management monitor node you can display the exceptions under Start of the navigation path Alert Next navigation step Exception End of the navigation path. From this node you can also navigate to the faulty warehouse order using the monitor method Display WO of WT. Here you can confirm warehouse tasks 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 With History option for your exception code.

In addition, you can configure your previously mentioned exceptions to raise an alert in the Alert Monitor by maintaining a follow-on alert for the respective exception code, business context, and execution step. You can find the Alert Monitor on the SAP Easy Access screen under Start of the navigation path SCM Basis Next navigation step Alert Monitor Next navigation step Alert Monitor End of the navigation path or by entering the transaction code /SAPAPO/AMON1. For information about alert profiles and alert notifications, see Alert Monitor.

Clearing Errors

When a pick-HU is rerouted to the clarification bin, you must check the HU, confirm any pick warehouse tasks 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 Alert Exception monitor node to identify the erroneous warehouse order. You can check here whether some of the pick warehouse tasks are still open. If multiple pick-HUs were sent to the clarification bin, you first have to check which one the product of the warehouse task was picked into. Since the remaining warehouse tasks could not be confirmed, they still point to the original destination and not to the pick-HU. When you have matched the warehouse tasks that are still open with the correct HUs, confirm the warehouse tasks in the foreground and change their destination to the appropriate pick-HU.

After solving the issue, we recommend that you mark the corresponding exception as solved using the Set Exception to Solved method of the Start of the navigation path Alert Next navigation step Exception End of the navigation path warehouse management monitor node. On a regular basis, solved exceptions can be reorganized using the report Reorganization of Exception Code Records (/SCWM/R_REORG_EXCEPTION_SOLVED).

After you finish processing a HU in the clarification bin, you must create an ad hoc warehouse task to the HU's original destination. You can create this ad hoc warehouse task using transaction Move Handling Unit (/SCWM/ADHU) which you can find on the SAP Easy Access screen under Start of the navigation path Extended Warehouse Management Next navigation step Work Scheduling Next navigation step Create Warehouse Task Without Reference End of the navigation path. If you work with process-oriented storage control, the system tries to determine the destination data automatically. For more information, see Process-Oriented Storage Control.