How To Fix WB2B336 - Different pricing types have been maintained for trading contract type

SAP Error Message - Details

• Message type: E = Error

• Message class: WB2B - Trading Contract

• Message number: 336

• Message text: Different pricing types have been maintained for trading contract type

What causes this issue?

Trading contract type &V1& has a different price determination type from
the trading contract type &V2&. This may cause inconsistencies in the
follow-on document, as the document conditions cannot be copied and the
price determination schemes are usually different.

System Response

The system does not allow this system setting.

How to fix this error?

Select trading contract types for which you have stored the same price
determination type.

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 WB2B336 - Different pricing types have been maintained for trading contract type ?

  The SAP error message WB2B336 indicates that there is a discrepancy in the pricing types maintained for a trading contract type. This error typically arises in the context of SAP's Commodity Management or similar modules where trading contracts are used.
  Cause:
  The error occurs when different pricing types are defined for the same trading contract type. This can happen due to:
  
  Inconsistent Configuration: The configuration settings for the trading contract type may have been altered or not uniformly maintained across different areas of the system.
  Multiple Pricing Types: The system may have multiple pricing types defined for the same contract type, leading to confusion during processing.
  Master Data Issues: The master data associated with the trading contract may not be aligned with the expected pricing types.
  
  Solution:
  To resolve the WB2B336 error, you can follow these steps:
  
  
  Check Configuration:
  
  Go to the configuration settings for the trading contract type in the SAP system.
  Ensure that the pricing types are consistently defined. You can do this by navigating to the relevant configuration path in SPRO (SAP Project Reference Object) and reviewing the settings.
  
  
  
  Review Pricing Types:
  
  Identify all the pricing types that are currently maintained for the trading contract type.
  If there are discrepancies, decide on a standard pricing type to be used and adjust the configuration accordingly.
  
  
  
  Adjust Master Data:
  
  Review the master data related to the trading contracts. Ensure that the pricing types used in the master data are consistent with the configuration.
  If necessary, update the master data to align with the correct pricing type.
  
  
  
  Testing:
  
  After making the necessary changes, test the trading contract creation or processing again to ensure that the error is resolved.
  
  
  
  Consult Documentation:
  
  If you are unsure about the correct pricing types or configurations, refer to SAP documentation or consult with your SAP functional consultant for guidance.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like SPRO for configuration, ME31K for creating contracts, or ME32K for changing contracts.
  SAP Notes: Check for any relevant SAP Notes that might address this specific error or provide additional guidance.
  User Forums: Consider visiting SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify and resolve the cause of the WB2B336 error in your SAP system.