How To Fix LB129 - Value &1 for characteristic &2 cannot be stored as numerator/denominator

LB129 - Overview

• Message type: E = Error

• Message class: LB - Logistics: Batch - Management

• Message number: 129

• Message text: Value &1 for characteristic &2 cannot be stored as numerator/denominator

What causes this issue?

You are maintaining a <DS:DE.ATWRT_WS>planned value</> or an actual
value for a characteristic for which you have defined
<DS:DE.LRMEI_WS>proportion or product units</> in the material master.
This value must be stored as a <DS:TX.MENGENUMRECHNUNG>numerator and
denominator for converting</> to the <DS:DE.MEINS>base unit of measure
</>. Numerators and denominators have a maximum length of five
characters.
The value you entered, &V1&, cannot be represented using numerators and
denominators.

System Response

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

How to fix this error?

Change the planned or actual value to a valid value.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message LB129 - Value &1 for characteristic &2 cannot be stored as numerator/denominator ?

  The SAP error message LB129 indicates that there is an issue with the values being assigned to a characteristic in the context of a calculation involving a numerator or denominator. This error typically arises in the context of SAP's Logistics or Production Planning modules, particularly when dealing with characteristics in the context of variant configuration or when defining formulas for calculations.
  
  Cause:
  The error message "LB129 Value &1 for characteristic &2 cannot be stored as numerator/denominator" usually occurs due to one of the following reasons:
  
  
  Invalid Value: The value being assigned to the characteristic is not valid for use as a numerator or denominator. This could be due to the value being non-numeric or not fitting the expected data type.
  
  
  Data Type Mismatch: The characteristic may be defined in a way that does not allow the value being assigned. For example, if the characteristic is defined as a string but a numeric value is