How To Fix >5760 - Request &1 has currency &2 and cannot be transferred

>5760 - Overview

• Message type: E = Error

• Message class: >5 -

• Message number: 760

• Message text: Request &1 has currency &2 and cannot be transferred

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 >5760 - Request &1 has currency &2 and cannot be transferred ?

  The SAP error message "5760 Request &1 has currency &2 and cannot be transferred" typically occurs during the transport of requests in the SAP system. This error indicates that there is a mismatch in currency settings between the source and target systems, which prevents the transport request from being processed.
  
  Cause:
  
  Currency Mismatch: The transport request contains objects that are defined in a specific currency (e.g., a configuration or master data object), and the target system does not support that currency.
  Different Currency Settings: The source and target systems may have different currency settings or configurations, leading to incompatibility.
  Transport Request Type: The type of transport request (e.g., customizing, workbench) may also affect how currency is handled.
  
  
  Solution:
  
  Check Currency Settings: Verify the currency settings in both the source and target systems. Ensure that they are aligned and support the same currencies.
  Adjust Transport Request: If possible, modify the transport request to remove or adjust the objects