How To Fix /SCTM/UI108 - BOLs cannot be created for planned shipments (&1 &2)

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCTM/UI -

• Message number: 108

• Message text: BOLs cannot be created for planned shipments (&1 &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 /SCTM/UI108 - BOLs cannot be created for planned shipments (&1 &2) ?

  The SAP error message /SCTM/UI108 BOLs cannot be created for planned shipments (&1 &2) typically occurs in the context of SAP Transportation Management (TM) when there is an issue with creating Bill of Lading (BOL) documents for planned shipments. This error can arise due to various reasons, and understanding the cause is essential for finding a solution.
  Possible Causes:
  
  Incomplete Shipment Data: The planned shipment may be missing required data or may not be fully configured, preventing the creation of BOLs.
  Status of the Shipment: The shipment might be in a status that does not allow for BOL creation (e.g., if it is not yet confirmed or is in a draft state).
  Configuration Issues: There may be configuration settings in the SAP TM system that are not set up correctly, affecting BOL generation.
  Authorization Issues: The user may not have the necessary authorizations to create BOLs for the specified shipments.
  Custom Logic or Enhancements: If there are custom developments or enhancements in the system, they might interfere with the standard process of BOL creation.
  
  Solutions:
  
  Check Shipment Data: Review the planned shipment details to ensure all required fields are filled out correctly. Make sure that the shipment is complete and ready for BOL creation.
  Verify Shipment Status: Ensure that the shipment is in a status that allows for BOL creation. If necessary, change the status to a valid one.
  Review Configuration: Check the configuration settings in SAP TM related to BOL creation. Ensure that all necessary settings are correctly configured.
  User Authorizations: Verify that the user attempting to create the BOL has the appropriate authorizations. If not, work with your SAP security team to grant the necessary permissions.
  Check for Custom Logic: If there are any custom developments or enhancements, review them to ensure they are not causing the issue. You may need to consult with your development team for further investigation.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with relevant transaction codes in SAP TM, such as /SCMTMS/SHIPMENT for managing shipments.
  Documentation: Refer to the official SAP documentation for Transportation Management for detailed information on BOL creation and shipment processing.
  Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  By systematically addressing these areas, you should be able to identify the root cause of the error and implement an appropriate solution.