How To Fix /ACCGO/UIS_MSG134 - Do not provide both SO and PO

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/UIS_MSG -

• Message number: 134

• Message text: Do not provide both SO and PO

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_MSG134 - Do not provide both SO and PO ?

  The SAP error message /ACCGO/UIS_MSG134 with the description "Do not provide both SO and PO" typically occurs in the context of the SAP system when there is an attempt to process a transaction that involves both a Sales Order (SO) and a Purchase Order (PO) simultaneously, which is not allowed.
  Cause:
  The error arises because the system is designed to handle either a Sales Order or a Purchase Order for a particular transaction, but not both at the same time. This is often seen in scenarios where the system expects a clear distinction between sales and procurement processes, and providing both identifiers leads to ambiguity in processing.
  Solution:
  To resolve this error, you should:
  
  
  Identify the Transaction: Determine which transaction you are trying to execute that is causing the error. This could be related to goods movement, invoice processing, or any other transaction that involves SO and PO.
  
  
  Check Input Fields: Review the input fields in the transaction screen. Ensure that you are only entering either a Sales Order number or a Purchase Order number, but not both. 
  
  
  Modify the Input: If you have mistakenly entered both, remove one of the entries based on the context of your transaction. For example, if you are processing a sales order, ensure that only the Sales Order number is provided.
  
  
  Consult Documentation: If you are unsure about the specific requirements for the transaction, refer to the relevant SAP documentation or user guides that pertain to the module you are working with.
  
  
  Seek Help from SAP Support: If the issue persists or if you believe that the error is occurring inappropriately, 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 the transaction codes related to Sales Orders (e.g., VA01, VA02) and Purchase Orders (e.g., ME21N, ME22N) to understand their specific functionalities.
  SAP Modules: This error may be relevant in modules such as SAP SD (Sales and Distribution) and SAP MM (Materials Management), so understanding the processes in these modules can be beneficial.
  User Roles and Authorizations: Ensure that your user role has the necessary authorizations to perform the intended transaction, as sometimes restrictions can lead to unexpected errors.
  
  By following these steps, you should be able to resolve the error and proceed with your transaction in SAP.