How To Fix MM_PUR_SES087 - Item currency is not the same as the document currency.

SAP Error Message - Details

• Message type: E = Error

• Message class: MM_PUR_SES -

• Message number: 087

• Message text: Item currency is not the same as the document 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 MM_PUR_SES087 - Item currency is not the same as the document currency. ?

  The SAP error message MM_PUR_SES087 indicates that there is a mismatch between the item currency and the document currency in a purchasing document, such as a purchase order or a purchase requisition. This error typically arises when the currency used for a specific item does not match the currency used for the overall document.
  Cause:
  
  Currency Mismatch: The item in the purchasing document is assigned a different currency than the document itself. For example, if the document currency is set to USD, but the item currency is set to EUR, this error will occur.
  Configuration Issues: There may be configuration settings in the SAP system that allow for currency differences, but they are not set up correctly.
  Data Entry Errors: During the creation or modification of the purchasing document, the user may have inadvertently selected a different currency for the item.
  
  Solution:
  
  
  Check Currency Settings: Verify the currency settings for both the document and the item. Ensure that they are the same. You can do this by:
  
  Opening the purchasing document in SAP.
  Checking the currency field for the document and the item.
  
  
  
  Adjust Item Currency: If the item currency is incorrect, you can change it to match the document currency. This can usually be done in the item details section of the purchasing document.
  
  
  Review Configuration: If this issue occurs frequently, it may be necessary to review the configuration settings in the SAP system related to currency handling in purchasing documents. This may involve consulting with your SAP Basis or configuration team.
  
  
  Create a New Document: If the document is not yet saved or if it is easier, consider creating a new purchasing document with the correct currency settings from the start.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for more detailed guidance on handling currency settings in purchasing documents.
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like ME21N (Create Purchase Order) or ME22N (Change Purchase Order) to access and modify purchasing documents.
  Currency Types: Understand the different currency types in SAP, such as document currency, local currency, and group currency, to better manage currency settings.
  User Roles and Permissions: Ensure that users have the appropriate permissions to change currency settings in purchasing documents.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or refer to SAP Notes for any known issues or patches related to this error message.