How To Fix WSTI_WD007 - Enter the count date

SAP Error Message - Details

• Message type: E = Error

• Message class: WSTI_WD - Retail Store Physical Inventory Web Dynpro ABAP

• Message number: 007

• Message text: Enter the count date

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 WSTI_WD007 - Enter the count date ?

  SAP Error Message:
  
  WSTI_WD007: Enter the count date
  
  Cause:
  This error message appears in SAP Inventory Management or Warehouse Management processes when a required count date (physical inventory count date) has not been entered. The system expects a valid date to proceed with inventory count-related transactions, such as posting physical inventory documents or performing cycle counts.
  The count date is essential because it defines the date on which the inventory was physically counted, and it is used for valuation and reconciliation purposes.
  
  When does it occur?
  
  During physical inventory document creation or posting.
  When entering or processing cycle count data.
  When the system requires a count date for inventory adjustment postings.
  
  
  Solution:
  
  
  Enter the Count Date:
  
  When prompted by the message, enter the correct physical inventory count date.
  The date should correspond to the actual date when the inventory was counted.
  
  
  
  Check the Screen or Transaction:
  
  In transactions like MI01 (Create Physical Inventory Document), MI04 (Enter Inventory Count), or MI07 (Post Inventory Differences), ensure the count date field is filled.
  If the field is missing or not visible, check the screen layout or user parameters.
  
  
  
  Verify Customizing Settings:
  
  In some cases, the system might require a count date due to configuration in physical inventory settings.
  Check the configuration under Logistics ? Materials Management ? Physical Inventory ? Physical Inventory Document ? Define Document Types to ensure the count date is mandatory or optional as per business needs.
  
  
  
  User Authorization:
  
  Ensure the user has the necessary authorization to enter or modify the count date.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  MI01 – Create Physical Inventory Document
  MI04 – Enter Inventory Count
  MI07 – Post Inventory Differences
  MI22 – Change Physical Inventory Document
  
  
  
  Physical Inventory Process:
  
  The count date is critical for inventory valuation and reconciliation.
  Incorrect or missing count dates can lead to incorrect stock values or posting errors.
  
  
  
  SAP Notes / Documentation:
  
  Check SAP Notes related to physical inventory if the error persists despite entering the count date.
  Sometimes, patches or updates may address UI or validation issues related to this field.
  
  
  
  
  Summary:
  WSTI_WD007 occurs because the system requires a physical inventory count date to proceed. To resolve it, simply enter the correct count date in the relevant field during the physical inventory process. Verify configuration and user permissions if the problem continues.
  
  If you provide the exact transaction or scenario where this error occurs, I can give more tailored guidance.