How To Fix WSTI_DOC017 - Enter the planned count date

SAP Error Message - Details

• Message type: E = Error

• Message class: WSTI_DOC - Messages from Function Group WSTI_DOC

• Message number: 017

• Message text: Enter the planned 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_DOC017 - Enter the planned count date ?

  SAP Error Message:
  
  WSTI_DOC017 - Enter the planned count date
  
  Cause:
  This error occurs when you are trying to post or process a physical inventory document (cycle count or inventory count) in SAP, but the Planned Count Date field is missing or not entered. The system requires this date to schedule and manage the inventory counting process properly.
  The Planned Count Date is essential because it indicates when the physical inventory count is planned to take place. Without this date, the system cannot proceed with the document processing.
  
  When does it occur?
  
  During the creation or processing of a physical inventory document (e.g., transaction MI01, MI04, MI07).
  When the planned count date field is left blank or deleted.
  When customizing or user input does not provide this mandatory field.
  
  
  Solution:
  
  
  Enter the Planned Count Date:
  
  Go to the physical inventory document screen.
  Locate the field for Planned Count Date (often labeled as "Planned Count Date" or "Count Date").
  Enter a valid date when the physical inventory count is planned to be performed.
  Save or proceed with the document.
  
  
  
  Check Customizing Settings:
  
  If the field is not visible or mandatory, check the configuration in Inventory Management under:
  
  IMG Path: Logistics ? Materials Management ? Physical Inventory ? Physical Inventory Documents ? Define Document Types for Physical Inventory
  
  
  Ensure that the document type you are using requires and allows entry of the planned count date.
  
  
  
  User Training:
  
  Train users to always enter the planned count date when creating or editing physical inventory documents.
  
  
  
  Program or Screen Variant:
  
  If this error occurs in a custom program or screen variant, ensure that the planned count date field is included and mandatory.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  MI01 – Create Physical Inventory Document
  MI02 – Change Physical Inventory Document
  MI04 – Enter Count Results
  MI07 – Post Inventory Differences
  
  
  
  Physical Inventory Process:
  
  The planned count date helps in scheduling and controlling the inventory count.
  It is used in reporting and audit trails to verify when the count was supposed to happen.
  
  
  
  SAP Notes / Documentation:
  
  Check SAP Notes related to physical inventory if the problem persists.
  Refer to SAP Help Portal for Physical Inventory Management.
  
  
  
  
  Summary:
  
  Cause: Planned Count Date is missing in the physical inventory document.
  Solution: Enter a valid planned count date before saving or posting the document.
  Additional: Verify customizing and user training to prevent recurrence.
  
  
  If you need further assistance, please provide the transaction code and context where the error occurs.