How To Fix /SCMTMS/TOR568 - FU &1 incompatible with booking &2 with ACS Status 'Not Checked'

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TOR -

• Message number: 568

• Message text: FU &1 incompatible with booking &2 with ACS Status 'Not Checked'

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/TOR568 - FU &1 incompatible with booking &2 with ACS Status 'Not Checked' ?

  The SAP error message /SCMTMS/TOR568 indicates that there is an incompatibility between a freight unit (FU) and a booking in the Transportation Management System (TMS). The specific message states that the freight unit (FU) &1 is incompatible with the booking &2, and the ACS (Advanced Cargo Security) status is 'Not Checked'.
  Cause:
  
  
  Incompatibility of Freight Unit and Booking: This error typically arises when the characteristics of the freight unit do not match the requirements of the booking. This could be due to various factors such as:
  
  Different transportation modes.
  Mismatched weight or volume constraints.
  Different handling requirements.
  Incompatible delivery dates or times.
  
  
  
  ACS Status 'Not Checked': The ACS status indicates that the security checks for the cargo have not been performed. This could mean that the system has not validated the freight unit against the security requirements for the booking.
  
  
  Solution:
  
  
  Check Freight Unit and Booking Details: Review the details of both the freight unit and the booking to identify any discrepancies. Ensure that:
  
  The transportation mode is the same for both.
  The weight and volume of the freight unit are within the limits specified in the booking.
  The handling requirements are compatible.
  The delivery dates and times align.
  
  
  
  Perform ACS Checks: If the ACS status is 'Not Checked', you may need to perform the necessary security checks. This can involve:
  
  Running the ACS validation process in the system.
  Ensuring that all required security documentation is in place.
  
  
  
  Adjust Freight Unit or Booking: If you find that the freight unit and booking are indeed incompatible, you may need to either:
  
  Modify the freight unit to meet the booking requirements.
  Create a new booking that matches the characteristics of the freight unit.
  
  
  
  Consult Documentation: Refer to SAP documentation or help resources for more detailed guidance on handling freight units and bookings in TMS.
  
  
  Contact Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional troubleshooting steps.
  Transaction Codes: Familiarize yourself with transaction codes related to TMS, such as /SCMTMS/FU for freight units and /SCMTMS/BOOKING for bookings, to facilitate easier navigation and troubleshooting.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, providing insights or solutions from other users' experiences.
  
  By following these steps, you should be able to identify the cause of the error and implement a suitable solution.