How To Fix /SCWM/CON158 - Fixed bin not determined (storage type: &1, storage type group: &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCWM/CON -

• Message number: 158

• Message text: Fixed bin not determined (storage type: &1, storage type group: &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 /SCWM/CON158 - Fixed bin not determined (storage type: &1, storage type group: &2) ?

  The SAP error message /SCWM/CON158 Fixed bin not determined (storage type: &1, storage type group: &2) typically occurs in the context of warehouse management when the system is unable to determine a fixed bin for a specific storage type and storage type group during a putaway or stock transfer process.
  Cause:
  
  Configuration Issues: The storage type or storage type group may not be properly configured in the system. This includes missing or incorrect settings for fixed bins.
  Master Data Issues: The material master data may not be correctly set up for the specific storage type or storage type group.
  Warehouse Process Type: The warehouse process type may not be correctly defined or linked to the storage type.
  Stock Type: The stock type of the material may not be compatible with the fixed bin settings.
  No Available Bins: There may be no available fixed bins in the specified storage type for the material being processed.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the configuration settings for the storage type and storage type group in the SAP system.
  Ensure that fixed bins are defined and that the settings are correct.
  
  
  
  Review Material Master Data:
  
  Check the material master data for the material in question.
  Ensure that the storage type and storage type group are correctly assigned.
  
  
  
  Verify Warehouse Process Type:
  
  Check the warehouse process type settings to ensure they are correctly linked to the storage type.
  Make sure that the process type allows for the use of fixed bins.
  
  
  
  Check Stock Type:
  
  Ensure that the stock type of the material is compatible with the fixed bin settings.
  If necessary, adjust the stock type or the fixed bin settings.
  
  
  
  Inspect Available Bins:
  
  Check if there are any available fixed bins in the specified storage type.
  If there are no available bins, you may need to create new fixed bins or adjust the existing ones.
  
  
  
  Debugging:
  
  If the issue persists, consider using transaction codes like /SCWM/PRDI (for putaway) or /SCWM/PRDI (for stock transfer) to analyze the process and identify where the determination fails.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SCWM/PRDI, /SCWM/PRDI, and others related to warehouse management.
  SAP Notes: Check for any SAP Notes related to this error message for potential patches or updates that may resolve the issue.
  Documentation: Review SAP documentation on warehouse management and fixed bin management for best practices and configuration guidelines.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.