How To Fix /PF1/MSG_EH_E721 - Cannot connect to AM system; error while getting external currency

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/MSG_EH_E -

• Message number: 721

• Message text: Cannot connect to AM system; error while getting external currency

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 /PF1/MSG_EH_E721 - Cannot connect to AM system; error while getting external currency ?

  The SAP error message /PF1/MSG_EH_E721 Cannot connect to AM system; error while getting external currency typically indicates an issue with the connection to the Asset Management (AM) system or a problem retrieving external currency information. Here are some potential causes, solutions, and related information for this error:
  Causes:
  
  Network Issues: There may be network connectivity problems between the SAP system and the Asset Management system.
  Configuration Issues: The configuration settings for the connection to the AM system may be incorrect or incomplete.
  Authorization Issues: The user may not have the necessary authorizations to access the AM system.
  System Downtime: The AM system may be down for maintenance or experiencing issues.
  Data Issues: There may be issues with the data being requested, such as missing or incorrect currency information.
  
  Solutions:
  
  
  Check Network Connectivity:
  
  Ensure that the SAP system can reach the AM system over the network. You can use tools like ping or traceroute to test connectivity.
  
  
  
  Review Configuration Settings:
  
  Check the configuration settings in the SAP system for the connection to the AM system. This may include verifying the RFC destination settings in transaction SM59.
  Ensure that the connection type (e.g., TCP/IP) and other parameters are correctly set.
  
  
  
  Verify User Authorizations:
  
  Ensure that the user has the necessary authorizations to access the AM system. This may involve checking roles and profiles assigned to the user.
  
  
  
  Check AM System Status:
  
  Verify if the AM system is up and running. If it is down, coordinate with the relevant team to resolve the issue.
  
  
  
  Review Currency Data:
  
  Check if the external currency data is correctly maintained in the system. This may involve reviewing currency settings in the configuration.
  
  
  
  Consult Logs:
  
  Check the application logs (transaction SLG1) for more detailed error messages that may provide additional context for the issue.
  
  
  
  Contact Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support or your internal IT support team for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM59 (RFC Destinations), SLG1 (Application Log), and SE37 (Function Module) to troubleshoot the issue.
  Documentation: Review SAP documentation related to Asset Management and currency settings for additional insights.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide patches related to this error.
  
  By following these steps, you should be able to identify and resolve the issue causing the error message.