How To Fix UACC061 - Surcharge call is not possible in system &1

UACC061 - Overview

• Message type: E = Error

• Message class: UACC - Message Class for Concurrent Costing Adapter

• Message number: 061

• Message text: Surcharge call is not possible in system &1

What causes this issue?

The template call is not possible in system &v1&.
This may be the result of one of the following reasons:
The necessary RFC function modules have not been implemented in target
system &v1&.
The RFC connection to target system &v1& does not work.

How to fix this error?

Make sure that the necessary RFC function modules have been implemented
in target system &v1&. If you cannot solve the problem in this way,
inform your system administrator.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message UACC061 - Surcharge call is not possible in system &1 ?

  The SAP error message UACC061, which states "Surcharge call is not possible in system &1," typically occurs in the context of surcharge processing in SAP systems, particularly in the area of billing or invoicing. This error can arise due to various reasons, and understanding the cause and potential solutions is essential for resolving the issue.
  Causes:
  
  
  
  Configuration Issues: The system may not be properly configured to handle surcharges. This could include missing or incorrect settings in the pricing procedure or condition types related to surcharges.
  
  
  Missing Master Data: Required master data, such as customer or material master records, may be incomplete or missing. This can prevent the system from processing surcharge calls.
  
  
  Incompatibility with Document Type: The document type being used may not support surcharge processing. Certain document types may have restrictions on surcharge applications.
  
  
  System Settings: The system settings for surcharge processing may not be activated or may be incorrectly set up.
  
  
  Version or Patch