How To Fix OD008 - No TSW shipping types have been found, check tables T173 + TVTR.

SAP Error Message - Details

• Message type: E = Error

• Message class: OD - IS-Oil: TSW Traders' and Schedulers' Workbench messages

• Message number: 008

• Message text: No TSW shipping types have been found, check tables T173 + TVTR.

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 OD008 - No TSW shipping types have been found, check tables T173 + TVTR. ?

  The SAP error message OD008 indicates that the system could not find any TSW (Transportation Shipping Workbench) shipping types in the relevant tables (T173 and TVTR). This error typically occurs in the context of transportation management and logistics execution processes.
  Cause:
  
  Missing Configuration: The most common cause of this error is that the necessary shipping types have not been configured in the system. This could be due to missing entries in the T173 (Shipping Types) or TVTR (Transportation Shipping Types) tables.
  Incorrect Settings: There may be incorrect or incomplete settings in the configuration of the Transportation Management module.
  Transport Layer Issues: If the system is newly implemented or recently upgraded, there may be issues with the transport layer that prevent the shipping types from being recognized.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to view or access the shipping types.
  
  Solution:
  
  
  Check Configuration:
  
  Go to the transaction code SPRO (SAP Project Reference Object) and navigate to the relevant configuration for Transportation Management.
  Ensure that the shipping types are defined correctly in the TSW settings.
  Verify that the shipping types are assigned to the relevant transportation lanes and routes.
  
  
  
  Review Tables:
  
  Use transaction SE11 or SE16 to check the contents of tables T173 and TVTR.
  Ensure that there are valid entries for the shipping types you are trying to use.
  
  
  
  Create/Update Shipping Types:
  
  If there are no entries in the tables, you may need to create new shipping types or update existing ones.
  Ensure that all necessary fields are filled out correctly.
  
  
  
  Check User Authorizations:
  
  Verify that the user has the necessary authorizations to access the shipping types.
  Consult with your SAP security team if needed.
  
  
  
  Transport Layer:
  
  If the issue arose after a transport, check if the transport was successful and if all necessary objects were included.
  You may need to re-transport the relevant configuration if there were issues.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help notes related to TSW and shipping types for additional guidance.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SPRO (to access configuration)
  SE11/SE16 (to view table contents)
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Community Forums: Consider searching or posting in SAP community forums for insights from other users who may have encountered the same issue.
  
  By following these steps, you should be able to identify the root cause of the OD008 error and implement the necessary solutions to resolve it.