How To Fix 67_RFC321 - Currency should be &1

SAP Error Message - Details

• Message type: E = Error

• Message class: 67_RFC - Message Class for RFC Modules

• Message number: 321

• Message text: Currency should be &1

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 67_RFC321 - Currency should be &1 ?

  The SAP error message "67_RFC321 Currency should be &1" typically indicates that there is a mismatch or an issue with the currency being used in a transaction or a function module call. This error often arises in scenarios involving Remote Function Calls (RFC) where the expected currency does not match the currency being passed in the request.
  Cause:
  
  Currency Mismatch: The currency being sent in the RFC call does not match the expected currency defined in the system or in the configuration.
  Configuration Issues: There may be configuration settings in the SAP system that define which currencies are valid for certain transactions or function modules.
  Data Entry Errors: Incorrect data entry in the transaction or during the setup of the RFC call can lead to this error.
  Master Data Issues: The master data (like customer or vendor records) may not have the correct currency settings.
  
  Solution:
  
  Check Currency Settings: Verify the currency settings in the relevant configuration areas (e.g., company code settings, controlling area settings).
  Review RFC Call Parameters: Ensure that the parameters being passed in the RFC call include the correct currency. This may involve checking the code or the data being sent.
  Validate Master Data: Check the master data for the entities involved (customers, vendors, etc.) to ensure that the correct currency is assigned.
  Transaction Currency: If applicable, ensure that the transaction currency matches the expected currency for the transaction type being processed.
  Consult Documentation: Review SAP documentation or notes related to the specific function module or transaction to understand the expected currency requirements.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional context.
  Transaction Codes: Use transaction codes like SE37 (Function Module) or SE80 (Object Navigator) to analyze the function module that is causing the error.
  Debugging: If you have access, consider debugging the RFC call to see the exact parameters being passed and identify where the mismatch occurs.
  User Roles and Authorizations: Ensure that the user executing the transaction has the necessary authorizations to work with the specified currency.
  
  If the issue persists after checking these areas, it may be beneficial to consult with your SAP Basis or functional team for further investigation.