How To Fix /SCTM/OCB_EDI005 - Source category &1 does not exist in table /SCTM/TSOURCCAT

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCTM/OCB_EDI -

• Message number: 005

• Message text: Source category &1 does not exist in table /SCTM/TSOURCCAT

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/OCB_EDI005 - Source category &1 does not exist in table /SCTM/TSOURCCAT ?

  The SAP error message /SCTM/OCB_EDI005 Source category &1 does not exist in table /SCTM/TSOURCCAT typically indicates that the system is trying to reference a source category that is not defined in the specified table (/SCTM/TSOURCCAT). This error is often encountered in the context of SAP Supply Chain Management (SCM) or SAP Transportation Management (TM) when dealing with EDI (Electronic Data Interchange) processes.
  Cause:
  
  
  Missing Source Category: The source category specified in the error message (&1) does not exist in the /SCTM/TSOURCCAT table. This could be due to:
  
  The source category not being created or configured in the system.
  A typo or incorrect reference in the configuration or data being processed.
  Data migration issues where the source category was not properly imported.
  
  
  
  Configuration Issues: The configuration settings for EDI or the specific process may not be set up correctly, leading to the system looking for a non-existent source category.
  
  
  Solution:
  
  
  Check the Source Category:
  
  Verify the source category that is causing the error. You can do this by checking the relevant configuration or the data being processed.
  Use transaction code SE11 to view the /SCTM/TSOURCCAT table and check if the source category exists.
  
  
  
  Create or Update the Source Category:
  
  If the source category does not exist, you may need to create it. This can typically be done through the relevant configuration transaction in SAP.
  If it exists but is not correctly configured, you may need to update it to ensure it meets the requirements of your EDI process.
  
  
  
  Review Configuration Settings:
  
  Check the configuration settings related to EDI and ensure that all necessary source categories are defined and correctly linked to the relevant processes.
  Ensure that any mappings or settings that reference the source category are correct.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help resources related to the specific module you are working with (e.g., SCM, TM) for guidance on configuring source categories.
  
  
  
  Contact SAP Support:
  
  If you are unable to resolve the issue, consider reaching out to SAP support for assistance, especially if this is a production environment.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SPRO (for configuration), SE11 (for table display), and SE80 (for development objects).
  SAP Notes: Check for any SAP Notes related to this error message or the specific module you are working with, as they may provide additional insights or patches.
  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 solution to resolve it.