How To Fix /SCMTMS/PLN_VSR_OL267 - &1 has shipping type &2 and must not be planned separately

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/PLN_VSR_OL -

• Message number: 267

• Message text: &1 has shipping type &2 and must not be planned separately

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 /SCMTMS/PLN_VSR_OL267 - &1 has shipping type &2 and must not be planned separately ?

  The SAP error message /SCMTMS/PLN_VSR_OL267 typically occurs in the context of SAP Transportation Management (TM) when there is an issue with the planning of transportation orders or shipments. The message indicates that a specific shipping type is not allowed to be planned separately, which can lead to issues in the transportation planning process.
  Cause:
  The error message is triggered when:
  
  Shipping Type Configuration: The shipping type associated with the transportation order or shipment is configured in such a way that it does not allow for separate planning. This could be due to business rules or settings in the system that dictate how certain types of shipments should be handled.
  Planning Group Settings: The planning group settings may restrict certain shipping types from being planned independently.
  Master Data Issues: There may be inconsistencies or missing data in the master data related to the shipping type or the transportation order.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Shipping Type Configuration:
  
  Go to the configuration settings for shipping types in SAP TM.
  Verify if the shipping type in question is set to allow separate planning. If not, you may need to adjust the configuration or use a different shipping type that allows for separate planning.
  
  
  
  Review Planning Group Settings:
  
  Check the planning group settings to ensure that the shipping type is included in the appropriate planning group that allows for separate planning.
  
  
  
  Examine Master Data:
  
  Review the master data for the transportation order or shipment to ensure that all necessary information is complete and accurate.
  Make sure that the shipping type is correctly assigned and that there are no discrepancies.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for more detailed information on the specific shipping type and its planning rules.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They can provide insights based on the specific configuration and version of your SAP system.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like /SCMTMS/PLN for planning or /SCMTMS/ORD for order management to investigate further.
  SAP Notes: Check for any relevant SAP Notes that might address known issues or provide patches related to this error message.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.