How To Fix VH544 - Pricing error: Data record sources are not supported (condition type &1).

VH544 - Overview

• Message type: E = Error

• Message class: VH - SD pricing

• Message number: 544

• Message text: Pricing error: Data record sources are not supported (condition type &1).

What causes this issue?

A data record source is activated in Customizing for the condition type
&V1&.
If pricing is called from SAP S/4HANA for customer management, this
function is not supported.

System Response

The condition record is deactivated and a pricing error is raised. This
means that your business transaction cannot be completed.

How to fix this error?

Contact your system administrator.

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

Procedure for System Administrators

Deactivate the data record source function in Customizing for the
condition type.
For more information about settings for pricing, see Customizing for
<LS>Customer Management</> under <LS>Basic Functions</> -> <LS>Pricing
</> -> <LS>Configure Pricing</>.
For more information about non-supported pricing functions in customer
management, search for <LS>Pricing Functions Not Supported in Customer
Management</> in the relevant version of <LS>SAP S/4HANA for customer
management </>on <LS>SAP Help Portal</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message VH544 - Pricing error: Data record sources are not supported (condition type &1). ?

  Certainly! Here's a detailed explanation for the SAP error message:
  
  SAP Error Message:
  VH544 - Pricing error: Data record sources are not supported (condition type &1).
  
  
  Cause:
  This error occurs during pricing in Sales and Distribution (SD) when the system encounters a condition type that is assigned to a data record source which is not supported in the current pricing procedure or context.
  More specifically:
  
  The condition type (&1) is linked to a data record source that the system cannot process in the current pricing scenario.
  This often happens if the condition record is maintained with a data record source that is incompatible with the pricing procedure or the sales document type.
  For example, the condition record might be maintained for a data record source like "Info Record" or "Contract" but the pricing procedure or sales document does not support that source.
  It can also occur if the condition type is assigned to a data record source that is