How To Fix BORGR649 - Movement type &1 not allowed as it is not assigned to the item category

SAP Error Message - Details

• Message type: E = Error

• Message class: BORGR - Messages Multi-Level Goods Receipt

• Message number: 649

• Message text: Movement type &1 not allowed as it is not assigned to the item category

What causes this issue?

This movement type is not allowed since no movement type has been
assigned for the current item category.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Check or make the following setting in Customizing:
In Customizing for Logistics Execution in the IMG activity Shipping ->
Deliveries -> <DS:TRAN.0VLP>Define Item Categories for Deliveries</>
you have to assign a movement type to the cuurent item category in the
detail screen.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message BORGR649 - Movement type &1 not allowed as it is not assigned to the item category ?

  The SAP error message BORGR649 indicates that a specific movement type is not allowed for a particular item category in the context of inventory management or logistics. This typically occurs during goods movements, such as goods receipts, goods issues, or transfer postings, when the system checks the compatibility of the movement type with the item category defined in the material master or document.
  Cause:
  
  Movement Type Configuration: The movement type you are trying to use is not configured to be used with the specified item category in the system. This can happen if the movement type is not assigned to the item category in the configuration settings.
  Item Category Settings: The item category may have restrictions that prevent certain movement types from being used. This is often defined in the material master or in the configuration settings for inventory management.
  Material Master Data: The material master data may not be set up correctly, leading to incompatibility between the movement type and the item category.
  
  Solution:
  
  
  Check Movement Type Configuration:
  
  Go to the transaction code OMJJ (or SPRO -> Logistics Execution -> Inventory Management -> Movement Types -> Define Movement Types).
  Verify that the movement type in question is correctly configured and assigned to the relevant item categories.
  
  
  
  Review Item Category Settings:
  
  Check the item category settings in the material master (transaction code MM03).
  Ensure that the item category allows the movement type you are trying to use.
  
  
  
  Adjust Material Master Data:
  
  If necessary, update the material master data to ensure that the item category is compatible with the movement type.
  You can do this by using transaction code MM02 to modify the material master.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or consult with your SAP functional consultant to understand the specific configurations and settings that may be affecting the movement type and item category relationship.
  
  
  
  Testing:
  
  After making the necessary changes, perform a test transaction to ensure that the error no longer occurs.
  
  
  
  Related Information:
  
  Movement Types: Movement types in SAP are used to define the type of inventory movement (e.g., goods receipt, goods issue, transfer posting) and have specific configurations that determine their behavior.
  Item Categories: Item categories are used in the context of purchasing and inventory management to classify items and determine how they behave in transactions.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues or provide additional guidance related to movement types and item categories.
  
  If the issue persists after following these steps, it may be beneficial to engage with your SAP support team or a consultant who can provide deeper insights into the configuration and potential issues in your specific SAP environment.