Enterprise Resource Planning Blogs by SAP
Get insights and updates about cloud ERP and RISE with SAP, SAP S/4HANA and SAP S/4HANA Cloud, and more enterprise management capabilities with SAP blog posts.
Showing results for 
Search instead for 
Did you mean: 
Product and Topic Expert
Product and Topic Expert

Why is exception handling important? 

Exception handling configuration for a verify step plays a pivotal role in shaping the behavior of a workflow. It tells the system on how to end or restart a workflow based on specified settings. Without properly defined exception handling, workflows might not behave in the way you would expect them to, which can cause problems. 

What should I pay attention to when I define a workflow? 

The approach to defining a workflow depends on the starting point. SAP offers a pre-delivered workflow for General Journal Entry Verification, which can be copied and customized. When creating a workflow by duplicating this template, the exception handling for verification and post steps is automatically defined as illustrated in the screenshot below. Pay close attention to the following settings: 

  • Required Action: Redo General Journal Entry 
  • Action Result: Restart Workflow 


On the other hand, when you create a workflow from scratch, you see different default settings. The initial configurations include "Do nothing" for Required Action and "Cancel workflow" for Action Result.  

With or without Redo? What’s the difference? 

It is essential to customize these settings in alignment with your business requirements. If you do not, the workflow might automatically terminate in the event of a rejected journal entry when you want it to be resubmitted. 

You can easily see the difference between the settings in the workflow history. Let’s see how the workflow history shows the workflow when the required action for exception handling is set to Do nothing or Redo General Journal Entry. 

 Without RedoWhen rejection happens: 


When the journal entry is resubmitted: 


As you can see from the screenshots, when the journal entry is rejected, the workflow ends. The system will initiate a new workflow after the resubmission of the journal entry or currency adjustment. 

With Redo+Restart workflow setting: 


When the journal entry is resubmitted:


From the log, you can clearly see that the resubmission of a journal entry relates to the existing workflow instead of initiating a new workflow. The setting tells the system to continue with the same workflow for the same journal entry even if it is rejected again. 

Adapting these settings ensures that the workflow responds appropriately to rejections, either ending or restarting based on the specified business logic. As you can see, it is important to tailor the configuration to suit the intricacies of your workflow so that you avoid unintended consequences. 

Put simply, when creating workflows, make sure you customize these settings to match your needs. The default options might not suit your situation and may cause workflows to end unexpectedly, but if you adjust the settings, you can ensure your workflow behaves in the way you want it to, either ending or restarting as required.  

For more information about procedures for creating workflows, please refer to the following topics on the SAP Help Portal: