How To Fix WRF_CONS005 - Cons.: Price test struct. mat.: Header total & unequal to comp. total &

WRF_CONS005 - Overview

• Message type: E = Error

• Message class: WRF_CONS - Retail Fashion: Consignment Processing Stock Transfers

• Message number: 005

• Message text: Cons.: Price test struct. mat.: Header total & unequal to comp. total &

What causes this issue?

The price test of a structured material - which was performed during
processing of vendor consignment goods - failed. The sum of the
components, &V2&, does not equal the sum in the header, &V1&. These two
prices must be equal or the test fails.

System Response

Processing is cancelled due to inconsistent data.

How to fix this error?

Check the structured material and its BOM.
Check the purchasing info records of the structured material (LOT, SET,
DISPLAY) and the corresponding components.
Make sure that the sum of components - including the quantity factor -
from the BOM is equal to the sum recorded in the header of the
structured material.

Procedure for System Administrators

Contact your system administrator.


You can deactivate the price test for each movement type in Customizing
for <LS>Retail Consignment Processing</>.
Please note, however, that any inconsistencies that occur due to
deactivated price tests are not covered by your Support agreement and
will not be dealt with free of charge.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WRF_CONS005 - Cons.: Price test struct. mat.: Header total & unequal to comp. total & ?

  The SAP error message:
  WRF_CONS005 Cons.: Price test struct. mat.: Header total & unequal to comp. total &
  typically occurs during the processing of a consignment or pricing scenario where the system performs a consistency check between the header-level price total and the sum of the component prices in a pricing structure.
  
  Cause
  
  The error indicates a mismatch between the total price at the header level and the sum of the component prices in the pricing structure for a material.
  This usually happens during pricing or invoice verification when the system expects the total price at the header (or document) level to exactly match the sum of all individual component prices.
  Possible reasons include:
  Rounding differences between header and component prices.
  Incorrect or incomplete pricing condition records.
  Custom pricing routines or user exits that modify prices inconsistently.
  Data inconsistencies in the pricing procedure or condition types.
  Manual price changes that are not reflected in all components.
  
  
  
  
  Solution
  
  
  Check Pricing Procedure and Condition Records:
  
  Verify