How To Fix /LIME/PI_CORE097 - Document &1 &2, item &3, already recounted (Recount terminated)

SAP Error Message - Details

• Message type: E = Error

• Message class: /LIME/PI_CORE -

• Message number: 097

• Message text: Document &1 &2, item &3, already recounted (Recount terminated)

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 /LIME/PI_CORE097 - Document &1 &2, item &3, already recounted (Recount terminated) ?

  The SAP error message /LIME/PI_CORE097 Document &1 &2, item &3, already recounted (Recount terminated) typically occurs in the context of inventory management or logistics processes, particularly when dealing with physical inventory recounts. This error indicates that the system has detected that a recount for the specified document and item has already been performed, and therefore, it cannot proceed with a new recount.
  Cause:
  
  Duplicate Recount Attempt: The most common cause of this error is that a recount has already been executed for the specified document and item. The system prevents multiple recounts to maintain data integrity.
  Incorrect Document Status: The document may be in a status that does not allow for recounting, or it may have been processed in a way that the recount is no longer valid.
  Configuration Issues: There may be configuration settings in the system that restrict recounting under certain conditions.
  
  Solution:
  
  Check Document Status: Verify the status of the document and item in question. If a recount has already been performed, you may need to review the results of that recount instead of attempting a new one.
  Review Recount History: Look into the recount history for the specific document and item to confirm that a recount has indeed been completed. This can usually be done through transaction codes related to inventory management.
  Consult with Inventory Management Team: If you are unsure about the recount status or need to perform a recount for a valid reason, consult with your inventory management or logistics team to determine the appropriate next steps.
  System Configuration: If you believe that the recount should be allowed, check the system configuration settings related to inventory recounts. You may need to adjust these settings or consult with your SAP Basis or configuration team.
  Error Logs: Review any error logs or messages that may provide additional context or details about why the recount was terminated.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as MI01 (Create Physical Inventory Document), MI02 (Change Physical Inventory Document), and MI04 (Enter Inventory Count) to manage physical inventory processes.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Documentation: Refer to SAP documentation on physical inventory processes for best practices and guidelines on how to manage recounts effectively.
  
  If the issue persists after following these steps, it may be necessary to escalate the problem to your SAP support team for further investigation.