How To Fix /ACCGO/SCP_MSG122 - Could not read purchasing organization from plant &1

/ACCGO/SCP_MSG122 - Overview

• Message type: E = Error

• Message class: /ACCGO/SCP_MSG -

• Message number: 122

• Message text: Could not read purchasing organization from plant &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 /ACCGO/SCP_MSG122 - Could not read purchasing organization from plant &1 ?

  The SAP error message /ACCGO/SCP_MSG122 Could not read purchasing organization from plant &1 typically indicates that the system is unable to retrieve the purchasing organization associated with a specific plant. This can occur in various scenarios, such as during the creation of purchase orders, material master records, or when executing certain transactions that require this information.
  Causes:
  
  Missing Configuration: The purchasing organization may not be properly assigned to the plant in the configuration settings.
  Data Inconsistency: There may be inconsistencies or missing entries in the relevant master data tables (e.g., plant or purchasing organization data).
  Authorization Issues: The user may not have the necessary authorizations to access the purchasing organization data.
  Transport Issues: If the system has recently undergone a transport of configuration or master data, it may not have been properly updated.
  
  Solutions:
  
  
  Check Configuration:
  
  Go to the transaction code SPRO and navigate to the following path:
  Materials Management > Purchasing > Assign Purchasing Organization to Plant.
  
  
  Ensure that