How To Fix /LIME/PI_CORE171 - Physical inventory procedure &1 not permitted in phys. inv. area &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /LIME/PI_CORE -

• Message number: 171

• Message text: Physical inventory procedure &1 not permitted in phys. inv. area &2

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_CORE171 - Physical inventory procedure &1 not permitted in phys. inv. area &2 ?

  The SAP error message /LIME/PI_CORE171 Physical inventory procedure &1 not permitted in phys. inv. area &2 typically occurs when there is an attempt to perform a physical inventory operation that is not allowed for the specified physical inventory procedure or area. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  Invalid Configuration: The physical inventory procedure specified (&1) is not configured to be used in the physical inventory area (&2). This could be due to settings in the configuration that restrict certain procedures to specific areas.
  Authorization Issues: The user may not have the necessary authorizations to perform the operation in the specified physical inventory area.
  Incorrect Procedure Assignment: The physical inventory procedure may not be correctly assigned to the physical inventory area in the system settings.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for physical inventory in SAP (Transaction code: SPRO).
  Navigate to Logistics > Inventory Management > Physical Inventory > Define Physical Inventory Procedures.
  Ensure that the physical inventory procedure (&1) is correctly assigned to the physical inventory area (&2).
  
  
  
  Review Physical Inventory Area Settings:
  
  Check the settings for the physical inventory area in the configuration to ensure that it allows the specified physical inventory procedure.
  You can find this under Logistics > Inventory Management > Physical Inventory > Define Physical Inventory Areas.
  
  
  
  User Authorizations:
  
  Verify that the user has the necessary authorizations to perform physical inventory operations in the specified area. This can be checked with the help of your SAP security team.
  
  
  
  Consult Documentation:
  
  Review the SAP documentation or help files related to physical inventory procedures and areas for any specific restrictions or requirements.
  
  
  
  Testing:
  
  After making any changes, test the process again to see if the error persists.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SPRO (to access configuration settings)
  MI01 (to create a physical inventory document)
  MI02 (to change a physical inventory document)
  MI03 (to display a physical inventory document)
  
  
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance.
  
  
  Community Forums: Consider searching or posting in SAP community forums for insights from other users who may have encountered the same issue.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.