How To Fix STGR168 - Purch. price rules prevent move of plant from reference plant &1 to &2

SAP Error Message - Details

• Message type: E = Error

• Message class: STGR - Hold store grouping messages

• Message number: 168

• Message text: Purch. price rules prevent move of plant from reference plant &1 to &2

What causes this issue?

Purchase price rules prevent reassignment to the target reference plant
that you selected.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Select another target reference plant or make corrections if you still
want to move the selected plants to the target reference plant. Check
all your settings and prices.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message STGR168 - Purch. price rules prevent move of plant from reference plant &1 to &2 ?

  The SAP error message STGR168 indicates that there are purchasing price rules that prevent the movement of a plant from a reference plant (denoted as &1) to another plant (denoted as &2). This typically occurs in the context of material master data management, particularly when trying to change the plant assignment for a material.
  Cause:
  The error is caused by the existence of purchasing price rules that are defined for the material in the reference plant. These rules dictate how purchasing prices are determined and can restrict the movement of materials between plants if certain conditions are not met. This is often related to:
  
  Price Control: The material may have specific price control settings that are tied to the reference plant.
  Purchasing Info Records: There may be existing purchasing info records that are linked to the reference plant, which need to be addressed before the plant can be changed.
  Conditions in Pricing: There may be conditions or agreements that are specific to the reference plant that do not apply to the target plant.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Review Purchasing Price Rules: Check the purchasing price rules associated with the material in the reference plant. You can do this by navigating to the material master data and reviewing the purchasing view.
  
  
  Adjust or Delete Info Records: If there are purchasing info records that are causing the issue, you may need to adjust or delete them. This can be done using transaction code ME11 (Create Purchasing Info Record) or ME12 (Change Purchasing Info Record).
  
  
  Check Price Control Settings: Ensure that the price control settings for the material are appropriate for the target plant. You may need to change the price control from moving average price (V) to standard price (S) or vice versa, depending on your business requirements.
  
  
  Consult with Purchasing Department: If you are unsure about the implications of changing purchasing price rules or info records, consult with your purchasing department or a colleague who is knowledgeable about procurement processes.
  
  
  Use Transaction Codes: You can use transaction codes like ME1M (Display Purchasing Info Records) to view existing records and understand what might be causing the restriction.
  
  
  Check for Dependencies: Ensure that there are no dependencies or conditions that are preventing the change. This may involve checking contracts, agreements, or other related documents.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME11, ME12, ME1M, and MM02 (Change Material).
  Material Master Views: Understand the different views of the material master, especially the purchasing view, to identify any discrepancies.
  SAP Notes: Check for any SAP Notes related to this error message for additional guidance or patches that may address the issue.
  Documentation: Review SAP documentation or help files for more detailed explanations of purchasing price rules and their implications.
  
  By following these steps, you should be able to identify the root cause of the STGR168 error and implement the necessary changes to resolve it.