How To Fix /ACCGO/UIS_MSG527 - Currency not allowed as input for PO/SO/STO reference document

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/UIS_MSG -

• Message number: 527

• Message text: Currency not allowed as input for PO/SO/STO reference document

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 /ACCGO/UIS_MSG527 - Currency not allowed as input for PO/SO/STO reference document ?

  The SAP error message /ACCGO/UIS_MSG527 Currency not allowed as input for PO/SO/STO reference document typically occurs when there is a mismatch or an issue with the currency settings in the system related to Purchase Orders (PO), Sales Orders (SO), or Stock Transport Orders (STO). Here’s a breakdown of the potential causes, solutions, and related information:
  Causes:
  
  Currency Mismatch: The currency used in the reference document (PO/SO/STO) does not match the currency settings in the configuration or the document type.
  Configuration Issues: The currency settings in the document type or the company code may not allow the specified currency.
  Master Data Issues: The vendor or customer master data may not be set up to allow transactions in the specified currency.
  Transaction Type Restrictions: Certain transaction types may have restrictions on the currencies that can be used.
  
  Solutions:
  
  
  Check Currency Settings:
  
  Verify the currency settings in the document type configuration. Ensure that the currency used in the reference document is allowed.
  Go to the configuration settings for the relevant document type and check the allowed currencies.
  
  
  
  Review Master Data:
  
  Check the vendor or customer master data to ensure that the currency is correctly set up. You can do this by navigating to the vendor or customer master record and reviewing the currency field.
  
  
  
  Adjust Document Currency:
  
  If possible, change the currency in the document to one that is allowed. This may involve creating a new document with the correct currency.
  
  
  
  Consult with SAP Basis or Functional Team:
  
  If the issue persists, consult with your SAP Basis or functional team to review the configuration settings and ensure that there are no underlying issues with the system setup.
  
  
  
  Check for Updates or Notes:
  
  Look for any SAP Notes or updates related to this error message. Sometimes, SAP releases patches or notes that address specific issues.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like ME23N (Display Purchase Order), VA03 (Display Sales Order), or MB03 (Display Material Document) to review the documents in question.
  SAP Help Documentation: Refer to the SAP Help Portal for detailed documentation on currency settings and configuration.
  User Exits or BAdIs: If your organization has custom developments, check if there are any user exits or BAdIs that might be affecting currency handling.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it. If the problem continues, further investigation into the specific configuration and data setup may be necessary.