How To Fix WI722 - Date is mandatory

SAP Error Message - Details

• Message type: E = Error

• Message class: WI - BPT Workflow: Messages from Info System

• Message number: 722

• Message text: Date is mandatory

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message WI722 - Date is mandatory ?

  SAP Error Message:
  
  WI722 - Date is mandatory
  
  Cause:
  The error message WI722 "Date is mandatory" occurs when a required date field in a workflow or related SAP transaction is left empty or not maintained. In SAP workflows, certain steps or tasks require a date to be entered to proceed, such as a due date, start date, or completion date. If this date is missing, the system triggers this error to enforce data completeness and consistency.
  Common scenarios where this error appears include:  
  
  Workflow tasks requiring a date input (e.g., deadline, planned date).  
  User decision steps where a date must be entered before continuing.  
  Custom workflows or standard SAP workflows where date parameters are mandatory.
  
  
  Solution:
  
  
  Enter the Required Date:
  
  When the error appears, check the screen or the workflow step for any date fields that are empty. Enter the appropriate date value (e.g., planned start date, due date).
  
  
  Check Workflow Container Elements:
  
  If you are a workflow administrator or developer, verify the workflow container elements to ensure that the date field is correctly mapped and populated before the step that triggers the error.
  
  
  Review Workflow Step Settings:
  
  In transaction SWDD (Workflow Builder), check the step that causes the error. Confirm that the date field is set as mandatory and that the workflow logic provides a value for it.
  
  
  Debug or Trace Workflow:
  
  Use transaction SWI1 (Workflow Log) or SWI2_FREQ to analyze the workflow execution and identify where the date is missing.
  
  
  Check Custom Code or Enhancements:
  
  If the workflow involves custom code (e.g., in methods or function modules), ensure that the date field is properly handled and passed.
  
  
  
  Related Information:
  
  
  Transaction Codes:  
  
  SWDD - Workflow Builder  
  SWI1 - Workflow Log  
  SWI2_FREQ - Workflow Runtime Analysis  
  SBWP - SAP Business Workplace (to check workflow inbox)
  
  
  
  SAP Notes:
  
  Sometimes SAP Notes provide fixes or clarifications related to workflow errors. Search for "WI722" or "Date is mandatory" in the SAP Support Portal.
  
  
  Workflow Container:
  
  The workflow container holds all the data elements used in the workflow. Missing or uninitialized container elements (like dates) often cause this error.
  
  
  User Input Screens:
  
  If the workflow step involves user input, ensure the screen layout includes the date field and that it is not hidden or disabled.
  
  
  
  Summary:
  
  Cause: Mandatory date field is empty in a workflow step or related transaction.  
  Solution: Enter the required date, verify workflow container and step settings, and ensure proper data flow.  
  Tools: Use workflow transactions (SWDD, SWI1) and debugging to identify and fix the issue.
  
  
  If you provide the exact context (e.g., which transaction or workflow step triggers the error), I can help with more specific guidance.