How To Fix WS268 - Contradiction in the settings of the store/central purchasing

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 268

• Message text: Contradiction in the settings of the store/central purchasing

What causes this issue?

The relationship of store &V1& to the head office cannot be uniquely
determined. The document contains head office &V2& while the master
data &V3& of accounting contains a different one.

System Response

It is not possible to release the document to Accounting.

How to fix this error?

Correct the master data setting. In particular, check whether the
partner functions of store &V1& are maintained correctly.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WS268 - Contradiction in the settings of the store/central purchasing ?

  SAP Error Message:
  
  WS268 - Contradiction in the settings of the store/central purchasing
  
  Cause:
  This error occurs when there is an inconsistency or contradiction in the configuration settings between the store (retail store) and central purchasing in SAP Retail. Specifically, the system detects conflicting parameters related to how purchasing is managed either locally at the store level or centrally.
  Typical scenarios causing this error include:
  
  The store is set up for central purchasing, but the central purchasing settings are not correctly maintained or contradict the store's settings.
  The store is configured for local purchasing, but the central purchasing parameters are still active or inconsistent.
  Mismatch in the assignment of purchasing organizations or purchasing groups between store and central purchasing.
  Incorrect or missing entries in customizing related to store master data or central purchasing settings.
  
  
  Solution:
  To resolve the WS268 error, follow these steps:
  
  
  Check Store Master Data:
  
  Go to the store master record (transaction WMS1 or relevant transaction in your SAP Retail system).
  Verify the purchasing settings, especially the flag indicating whether the store uses central purchasing or local purchasing.
  
  
  
  Check Central Purchasing Settings:
  
  Review the central purchasing configuration in customizing (SPRO path):
  
  Retail ? Master Data ? Store ? Define Central Purchasing
  Ensure that the central purchasing parameters are consistent and correctly assigned to the stores.
  
  
  
  
  
  Align Store and Central Purchasing Settings:
  
  If the store is set for central purchasing, ensure that the central purchasing organization and purchasing group are correctly assigned and active.
  If the store is set for local purchasing, make sure that central purchasing parameters are not conflicting or assigned incorrectly.
  
  
  
  Correct Contradictory Entries:
  
  Remove or correct any contradictory entries in the store master or central purchasing customizing.
  Check for any custom enhancements or user exits that might be enforcing contradictory logic.
  
  
  
  Transport and Test:
  
  After corrections, transport the changes if necessary.
  Test the purchasing process again to confirm the error is resolved.
  
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Service Marketplace for any notes related to WS268 or store/central purchasing contradictions.
  Transactions:
  
  Store Master Data Maintenance: WMS1, WMS2
  Customizing for Central Purchasing: SPRO ? Retail ? Master Data ? Store ? Define Central Purchasing
  
  
  Documentation: SAP Retail documentation on store master data and central purchasing setup.
  Common Pitfalls:
  
  Forgetting to maintain central purchasing parameters after changing store purchasing type.
  Inconsistent assignment of purchasing organizations or groups.
  Missing or incorrect entries in customizing tables like WMS_STORE or related tables.
  
  
  
  
  If you provide the exact scenario or transaction where the error occurs, I can help with more specific guidance.