How To Fix SOA_SD058 - You cannot use condition type &1 for pricing elements on header level.

SAP Error Message - Details

• Message type: E = Error

• Message class: SOA_SD - Messages for SOA Processing in SD

• Message number: 058

• Message text: You cannot use condition type &1 for pricing elements on header level.

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 SOA_SD058 - You cannot use condition type &1 for pricing elements on header level. ?

  The SAP error message SOA_SD058 indicates that there is an issue with the use of a specific condition type at the header level in the pricing procedure. This error typically arises when a condition type that is not allowed for header-level pricing is being used in a sales document.
  Cause:
  
  Condition Type Configuration: The condition type specified in the error message (represented as &1) is configured in such a way that it is not permitted to be used at the header level. This could be due to the settings in the pricing procedure or the condition type itself.
  Pricing Procedure: The pricing procedure assigned to the sales document may not allow certain condition types to be applied at the header level.
  Document Type: The document type being used may have restrictions on which condition types can be applied at the header level.
  
  Solution:
  
  
  Check Condition Type Configuration:
  
  Go to the transaction code V/06 to check the configuration of the condition type in question.
  Ensure that the condition type is set up correctly and is allowed for header-level pricing if that is your intention.
  
  
  
  Review Pricing Procedure:
  
  Use transaction code V/08 to review the pricing procedure assigned to the sales document.
  Check the condition type's assignment in the pricing procedure and ensure that it is allowed at the header level.
  
  
  
  Adjust Document Type Settings:
  
  Check the settings for the document type being used in the sales order. Ensure that the pricing procedure assigned to the document type allows the use of the condition type at the header level.
  
  
  
  Consult with Functional Consultant:
  
  If you are unsure about the configuration or the implications of changing settings, consult with an SAP SD functional consultant who can provide guidance based on your specific business requirements.
  
  
  
  Testing:
  
  After making any changes, test the sales document creation process to ensure that the error is resolved and that the pricing behaves as expected.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on the configuration of condition types and pricing procedures.
  Documentation: Review SAP documentation related to pricing procedures and condition types for a deeper understanding of how they interact and the rules governing their use.
  Transaction Codes:
  
  V/06: Condition Types
  V/08: Pricing Procedures
  V/02: Access Sequences
  
  
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.