How To Fix /ACCGO/SCP_MSG273 - Back to back pegging not allowed with same contract &1 in both legs

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/SCP_MSG -

• Message number: 273

• Message text: Back to back pegging not allowed with same contract &1 in both legs

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_MSG273 - Back to back pegging not allowed with same contract &1 in both legs ?

  The SAP error message /ACCGO/SCP_MSG273 indicates that there is an issue with back-to-back pegging in the context of supply chain planning or contract management. Specifically, it suggests that the same contract is being used in both legs of a back-to-back transaction, which is not allowed.
  Cause:
  The error typically arises in scenarios where:
  
  Back-to-Back Orders: You are trying to create a back-to-back order where both the supply and demand legs reference the same contract.
  Contract Configuration: The contract may not be set up to allow for back-to-back transactions in the way you are attempting.
  System Configuration: There may be system settings or constraints that prevent the use of the same contract in both legs of the transaction.
  
  Solution:
  To resolve this error, consider the following steps:
  
  
  Check Contract Usage:
  
  Review the contracts involved in the transaction. Ensure that you are not using the same contract for both the supply and demand legs of the back-to-back order.
  
  
  
  Modify Order Configuration:
  
  If possible, modify the order configuration to use different contracts for each leg. This may involve creating a new contract or selecting an existing one that is appropriate for the transaction.
  
  
  
  Review System Settings:
  
  Check the system settings related to back-to-back transactions. There may be configuration options that can be adjusted to allow for the desired behavior.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help resources specific to your version of SAP and the modules you are using. This can provide insights into the constraints and configurations related to back-to-back pegging.
  
  
  
  Contact SAP Support:
  
  If the issue persists and you cannot find a resolution, consider reaching out to SAP support for assistance. They can provide guidance based on your specific system configuration and business processes.
  
  
  
  Related Information:
  
  Back-to-Back Order Processing: Understand the principles of back-to-back order processing in SAP, including how it relates to supply chain management and contract management.
  Contract Management: Familiarize yourself with how contracts are managed within SAP, including the rules and configurations that govern their use in transactions.
  SAP Notes and Knowledge Base: Search for relevant SAP Notes or articles in the SAP Knowledge Base that may address similar issues or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.