How To Fix F5372 - Purchasing document has a different currency key

SAP Error Message - Details

• Message type: E = Error

• Message class: F5 - Document Editing

• Message number: 372

• Message text: Purchasing document has a different currency key

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 F5372 - Purchasing document has a different currency key ?

  The SAP error message F5372, which states "Purchasing document has a different currency key," typically occurs when there is a mismatch between the currency of the purchasing document (such as a purchase order) and the currency expected in the financial transaction or the currency of the vendor master data.
  Cause:
  
  Currency Mismatch: The currency of the purchasing document does not match the currency of the vendor or the currency defined in the financial transaction.
  Configuration Issues: There may be configuration settings in the SAP system that are not aligned, such as currency settings in the company code or purchasing organization.
  Master Data Issues: The vendor master data may be set up with a different currency than what is being used in the purchasing document.
  Document Type Settings: The document type used for the purchasing document may have specific currency settings that do not align with the transaction being processed.
  
  Solution:
  
  
  Check Currency Settings:
  
  Verify the currency of the purchasing document and ensure it matches the currency of the vendor master data.
  Check the currency settings in the company code and purchasing organization to ensure they are correctly configured.
  
  
  
  Update Vendor Master Data:
  
  If the vendor's currency needs to be changed, update the vendor master data to reflect the correct currency that matches the purchasing document.
  
  
  
  Review Document Type Configuration:
  
  Check the configuration of the document type used for the purchasing document to ensure it allows for the currency being used.
  
  
  
  Use Transaction Codes:
  
  Use transaction codes like ME23N (Display Purchase Order) to review the purchase order details and confirm the currency.
  Use MK03 (Display Vendor) to check the vendor's currency settings.
  
  
  
  Consult with SAP Support:
  
  If the issue persists, consider reaching out to your SAP support team or consulting SAP notes for any known issues or patches related to this error.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME21N (Create Purchase Order), ME22N (Change Purchase Order), and ME23N (Display Purchase Order).
  SAP Notes: Check SAP Notes for any updates or specific fixes related to error F5372.
  Documentation: Review SAP documentation regarding currency settings in purchasing and financial transactions for a deeper understanding of how currencies are managed in SAP.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.