How To Fix /SCMTMS/FAG_MSG395 - Matching charge type not found

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/FAG_MSG -

• Message number: 395

• Message text: Matching charge type 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/FAG_MSG395 - Matching charge type not found ?

  The SAP error message /SCMTMS/FAG_MSG395 Matching charge type not found typically occurs in the context of SAP Transportation Management (TM) when the system is unable to find a corresponding charge type for a specific charge or cost item in the transportation process. This can happen during various processes, such as freight settlement or charge calculation.
  Cause:
  
  Missing Charge Type Configuration: The charge type that is being referenced in the transaction does not exist in the system or is not properly configured.
  Incorrect Mapping: There may be an issue with the mapping between the charge types in the transportation management system and the financial accounting system.
  Data Inconsistency: There could be inconsistencies in the master data or transactional data that lead to the system being unable to find a matching charge type.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access certain charge types.
  
  Solution:
  
  
  Check Charge Type Configuration:
  
  Go to the configuration settings in SAP TM and verify that the charge types are correctly defined.
  Ensure that the charge type you are trying to use is active and properly set up in the system.
  
  
  
  Review Mapping Settings:
  
  Check the mapping between charge types in SAP TM and the corresponding financial accounting settings.
  Ensure that the charge types are correctly linked to the appropriate accounts in the financial system.
  
  
  
  Data Validation:
  
  Validate the master data related to the charge types. Ensure that all necessary data is complete and consistent.
  Check for any missing or incorrect entries in the relevant tables.
  
  
  
  Authorization Check:
  
  Verify that the user has the necessary authorizations to access and use the charge types in question.
  If needed, consult with your SAP security team to ensure proper access rights.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources for specific guidance on charge type configuration and troubleshooting.
  
  
  
  Debugging:
  
  If the issue persists, consider using debugging tools to trace the execution and identify where the error is occurring.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like /SCMTMS/CHARGE to manage charge types or /SCMTMS/FREIGHT for freight-related configurations.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Community Forums: Engage with SAP community forums or support channels for additional insights and solutions from other users who may have encountered similar issues.
  
  If the problem continues after following these steps, it may be beneficial to reach out to SAP support for further assistance.