How To Fix /SCMTMS/GT_CUST009 - Client &1, table &2: Customs activity &3 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/GT_CUST -

• Message number: 009

• Message text: Client &1, table &2: Customs activity &3 not found

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/GT_CUST009 - Client &1, table &2: Customs activity &3 not found ?

  The SAP error message /SCMTMS/GT_CUST009 typically indicates that there is a missing or incorrectly configured customs activity in the system. This error is related to the SAP Transportation Management (TM) module, specifically in the context of customs management.
  
  Cause:
  The error message can occur due to several reasons:
  
  Missing Configuration: The customs activity specified in the error message is not defined in the system. This could be due to incomplete configuration during the setup of customs management.
  Incorrect Data Entry: There may be a typo or incorrect entry in the customs activity field, leading to the system being unable to find the specified activity.
  Client-Specific Issues: The error may be specific to the client (indicated by Client &1), meaning that the customs activity might exist in other clients but not in the one you are working with.
  Transport Issues: If the configuration was recently transported from another system, it may not have been transported correctly, leading