How To Fix /SCMTMS/TCC_HL_MSG871 - Rule &1 applied; amount for charge item (type &2) not determined

SAP Error Message - Details

• Message type: E = Error

• Message class: /SCMTMS/TCC_HL_MSG -

• Message number: 871

• Message text: Rule &1 applied; amount for charge item (type &2) not determined

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/TCC_HL_MSG871 - Rule &1 applied; amount for charge item (type &2) not determined ?

  The SAP error message /SCMTMS/TCC_HL_MSG871 typically occurs in the context of SAP Transportation Management (TM) when there is an issue with the determination of charge items during the transportation charge calculation process. This error indicates that a specific rule (denoted by &1) was applied, but the system was unable to determine the amount for a charge item of a specified type (denoted by &2).
  Cause:
  
  Missing Configuration: The charge item type may not be properly configured in the system. This could include missing condition records or rules that define how charges should be calculated.
  Inconsistent Data: There may be inconsistencies or missing data in the master data (e.g., business partners, materials, etc.) that are required for the charge calculation.
  Incorrect Rule Application: The rule applied may not be suitable for the specific scenario, leading to the inability to determine the charge amount.
  Custom Logic: If there is custom logic implemented for charge determination, it may not be functioning correctly or may not cover all scenarios.
  
  Solution:
  
  Check Configuration: Review the configuration settings for charge item types in the SAP TM system. Ensure that all necessary condition records are created and that the rules are correctly defined.
  Review Master Data: Verify that all relevant master data is complete and accurate. This includes checking business partner data, transportation lanes, and any other relevant data that may impact charge determination.
  Analyze Rule Application: Investigate the specific rule that was applied (indicated by &1) to ensure it is appropriate for the charge item type (indicated by &2). You may need to adjust the rule or create additional rules to cover different scenarios.
  Debug Custom Logic: If there is custom logic involved in the charge determination process, debug the code to identify any issues that may be causing the failure to determine the charge amount.
  Consult Documentation: Refer to SAP documentation or notes related to charge determination in SAP TM for additional guidance and best practices.
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like /SCMTMS/CHARGE to review charge configurations or /SCMTMS/PRC to analyze pricing conditions.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide updates related to charge determination in SAP TM.
  Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance, providing them with the error message details and any relevant configuration settings.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.