Simple way to understand SAP EWM exception handling is to know what and when these exceptions are occurred to execute. This blog post explains you the basic understanding of SAP EWM exception codes that we need to know for what business context that user/system looking for and when these execution steps are running.
SAP Help explains exception as below:
The exception code basically tells us an exception situation in the warehouse. This exception situation occurs, for example, if system returns data does not match up with the actual situation in the warehouse. You can use exception code to communicate this to the system. You can then, for example, simply save the information, or can use it to trigger the system to start follow-up actions. For this purpose, there are connections available to the SAP Workflow, to the SAP Alert Framework, and to SAP Status Management.
Once we know what business context and the execution step, then we should configure follow-up actions like assigning internal process code and follow-on actions of workflow ID/alert.
This blog post explains in two sections one as “business context and execution steps” and second “define exception codes.”
Business context and Execution Steps:
EWM under Cross-Process Settings → Exception Handling → Maintain Business Context for exception codes.. see below some of the important business contexts
Define the SAP EWM exception codes:
Define the exception code by making assignments to the business context, the process code, and the exception code profile.
Configure follow-up actions: 1. Assign internal process codes. .2. Assign of a status management action ID like generate PI document or send email.
SAP delivers internal process codes that influence the behaviour of RF- or desktop-screen (CHBD – Change destination bin) or process differences (for example DIFF, BIDF, or BIDP).
The difference category defines the follow-up actions for the differences to either source bin or difference account.
You can create workflow start IDs. You define these IDs by making assignments for persistent ABAP classes and their events, including the workflow number.
You can assign available status management actions (block source bin for putaway) to influence the status of the affected object (bin) or you can set the customer-specific user status.
Exception handling supports the status change for bins and handling units.
You can assign the available alert types to categorize the alerts that will be displayed within the Alert Monitor.
Simple Scenarios using a standard SAP EWM Exception Codes
1. RF terminal picking
A warehouse employee has an order to remove 100 pieces from a storage bin. However, the storage bin shows only 80 then the employee enters an exception code, the system update the actual qty in the delivery and triggers Physical inventory document for the source bin.
2. RF terminal putaway
A warehouse employee has an order to put away 100 pieces into a storage bin. However, the storage bin is currently in maintenance. After the employee enters an exception code, the system sends an alert to the warehouse manager, and Physical inventory document for the bin with bin block for putaways and stock removals.
The first, you need to select a exception code for a warehouse with BIDF is an example.
Test configuration of Exception codes in SPRO
How do you know the Exception Codes was setup with details to see in one place for a business context, then you need to see below
” Test configuration of Exception codes in SPRO from the same IMG where exception handling avaiable
a) See below putaway business context (TPT)with step 04 RF HU WT
b) See below stock removal business context (TPI) with step 05 RF product WT
With all the above, we only know what and how we can use exception codes. We can learn more based on different client requirements and then configure and use through standard & customised programs in SAP EWM.
Configure Custom exception code for a specific business requirement.
Many warehouses where picking a short quantity with exception code trigger an action of creating a PI for the source bin or looking a product in another bin. Alon with this requirement we also had a scenario some products with package quantity where user under pick based against delivery quantity. In this case system need to update the delivery quantity with picked quantity and does not required an action to create a PI count for the source bin or do not require looking a product in another bin for short quantity. So in this case user need two exception codes for two different scenarios for picking a product. One exception code require a custom action another does not. We do the below two actions
A) Create a custom Exception code “SHRT” where user applies this when he really doing a shor picking of a product and system triggers PI count for the source bin and do custom action
B) Configuring a Exception code “DIFS” where user applies this when he is not doing a short pick but picked less quantity and system would change picked quantity as a delivery line quantity and does not trigger further action.
See steps for
A) Create a custom Exception code “SHRT”
Define SHRT exception for a business context TPI with step 5 for RF pick WT
Maintain process parameters with internal process code BIDP that allows to pick partial quantity
See next we had Follow-on action with custom work flow Id that was copied from standard WT02 and changed for our need.
Configuring a Exception code “DIFS”
Now see the second exception code where use standard exception code DIFS to configure with required action
now we can configure below we used process code “0001” which will adjust delivery document with WT picked quantity. This will not create further EWM delivery for the short quantuty, but if you want to then choose 0002 process that will create a EWM delivery right after picked quantity updated.
with the above setting we had two exception codes applied for two different purposes at the time of picking.
See below some more information from SAP help website for
You have defined your own exception codes for calling exception handling, and have assigned these to the internal exception codes defined by SAP.
Customizing for EWM under Cross-Process Settings Exception Handling Define Exception Codes
Scenario with delivery quantity updates
• If you adjust the delivery quantity using an exception code for an automatic delivery update, you must also have defined exception codes in Customizing for EWMand assigned them to the process codes. For more information, refer to the IMG for EWM under Cross-Process Settings Exception Handling Define Exception Codes .
• For both types of delivery quantity adjustment, you have also assigned partner roles to the process codes in Customizing as showen below for EWM under Cross-Process Settings Delivery Processing Process Codes Define Process Codes . If you record quantity differences for stock transfer orders for example, the partner you define here corresponds to the person who caused the delivery quantity difference. EWM saves delivery quantity differences for this partner and sends the information to SAP ERP. The only information EWM does not send to SAP ERP is information about delivery quantity differences for posting change deliveries, since these involve internal warehouse differences.
• If you are confirming a warehouse task or recording counting, on the SAP Easy Access screen choose Extended Warehouse Management Execution Confirm Warehouse Task or Execution Quality Inspection and Count , to specify an exception code. EWM assigns this exception code to a process code, corresponding to the settings you have made in Customizing. EWM then uses the delivery update to adjust the delivery quantity for each item, corresponding to the settings of the process code.
• If you are repacking delivery stock, on the SAP Easy Access screen choose Extended Warehouse Management Execution Packing – General . If you have defined the work center correspondingly in Customizing for EWM, then EWM displays the tab page Differences. For this, you have defined the work centre layout in the IMG for EWM under Master Data Work Center Specify Work Center Layout . You record the difference and specify an exception code. EWM maps this exception code to the relevant process code in the background and updates the delivery.
• For both types of delivery quantity adjustment, you have also defined in Customizing for EWM the partners for which EWM reports exceptions, namely process codes, to SAP ERP. For more information, see the IMG forEWM under Interfaces ERP Integration Delivery Processing Map Partner Roles from ERP System to EWM .
For more information of exception handling i recommend look documents in help.sap.com portal.