/SCMTMS/PLN_FUB119 - Cannot split &1 &2; FUB rule settings violated

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/PLN_FUB -

• Message number: 119

• Message text: Cannot split &1 &2; FUB rule settings violated

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.

AnswerBot

• What is the cause and solution for SAP error message /SCMTMS/PLN_FUB119 - Cannot split &1 &2; FUB rule settings violated ?

  The SAP error message /SCMTMS/PLN_FUB119 Cannot split &1 &2; FUB rule settings violated typically occurs in the context of SAP Transportation Management (TM) when there is an attempt to split a transportation requirement or a shipment, but the split violates the settings defined in the Freight Unit Building (FUB) rules.
  Cause:
  The error is caused by the following factors:
  
  FUB Rule Settings: The Freight Unit Building rules may have specific conditions that prevent the splitting of freight units based on certain criteria (e.g., weight, volume, or other attributes).
  Transportation Requirement Attributes: The attributes of the transportation requirement or shipment may not meet the criteria defined in the FUB rules, leading to a violation when a split is attempted.
  Configuration Issues: There may be misconfigurations in the FUB settings that do not align with the business processes or requirements.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Review FUB Rules: Check the FUB rules configured in your SAP TM system. Ensure that the rules allow for the splitting of freight units under the conditions you are trying to execute.
  
  Navigate to the FUB rule settings in the SAP TM configuration and review the conditions that are set for splitting.
  
  
  
  Adjust Transportation Requirement: If the transportation requirement or shipment does not meet the criteria for splitting, consider adjusting its attributes (e.g., weight, volume) to comply with the FUB rules.
  
  
  Consult Documentation: Refer to the SAP documentation or help resources related to Freight Unit Building and splitting rules to understand the specific conditions that may be causing the violation.
  
  
  Test Different Scenarios: If possible, test different scenarios to identify which specific attribute or condition is causing the error. This can help in pinpointing the exact issue.
  
  
  Consult with SAP Support: If the issue persists and you cannot identify the cause, consider reaching out to SAP support for assistance. They can provide insights based on the specific configuration and version of your SAP TM system.
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like /SCMTMS/FUB to access FUB settings or /SCMTMS/PLN for planning-related transactions.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide updates related to FUB rules and splitting.
  Community 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 cause of the error and implement a suitable solution.