web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Small and medium business | Business Central, N...
Suggested Answer

Decimal precission error in picking

(7) ShareShare
ReportReport
Posted on by 171
Hi all,
 
We are working with a basic warehouse configuration with only picking required. We have setup unit of measures for items, and at the time of posting a picking we are getting a precission error. As an example:
 
Item A has two units of measure, bags and boxes. Each box contains 4 bags. The bag is the Base unit of measure, and we have set 1 as decimal rounding precission.
 
Now we have a sales order with ona box of Item A. We create an inventory pick (confirmed that the line in the pick has 1 box). However, we do not have a full box in stock, only a bag. So in Qty. to handle (base) we introduce 1. The field Qty. to handle automatically populates with 0.25 boxes. We post and get the following error:
The value 0.25 of the field Qty to ship has less precission than required.
 
I believe the error is being produced in the Sales Order as Qty to ship belongs to that table, not to the pick itself.
 
Any guidance on how to solve this error? Maybe by updating the precission in the base unit of measure?
 
Thanks a lot in advance.
Regards,
I have the same question (0)
  • Suggested answer
    Jainam M. Kothari Profile Picture
    15,639 Super User 2025 Season 2 on at
    Hello,
     
    The error "The value 0.25 of the field Qty to ship has less precision than required" occurs because the Base Unit of Measure (bags, in your case) has a Decimal Rounding Precision set to 1, allowing only whole numbers.
     
    When you try to post a partial quantity (like 0.25 boxes = 1 bag), the system attempts to write a decimal into a field that only accepts integers, causing the error.
     
    Solution - Update the rounding precision for the base unit to allow decimals (e.g., 0.01)
     
  • Suggested answer
    Jun Wang Profile Picture
    8,202 Super User 2025 Season 2 on at
    You could try zero out the value you put in the UOM page of that item. 
  • xmp Profile Picture
    171 on at
    Thanks for your response Jainam. As per the link you provided:
     
    For example, imagine you're receiving one box that contains six items. When the box arrives at your warehouse, you discover that one of the six items is missing. You decide not to post the receipt of one box, but instead change the quantity received to five of six pieces. That decision would lead to a receipt of 4.99998 pieces, rather than five. On the Item Units of Measure page, the Quantity Rounding Precision field lets you specify a value that converts the quantity to a number that's easier to understand. Continuing with the example, we would enter 1 in the field to round up to an even five pieces.
     
    This is exactly my problem, but instead of receiving I'm sending. Maybe I'm missing something but from what I understand, if I setup the rounding precision to 0.01, following Microsoft's example I wouldn't be getting 5 pieces but 4.98, right? We decided to set rounding precision to 1 precisely to avoid decimals in our stock.
     
    Thanks in advance.
    Regards,
  • Suggested answer
    Andrés Arias Profile Picture
    4,190 Super User 2025 Season 2 on at
  • Gerardo Rentería García Profile Picture
    25,225 Most Valuable Professional on at

    Hi, good day
    I hope this can help you, and give you some hints.

    Set up item units of measure - Business Central | Microsoft Learn

    Rounding Unit Costs is Mayhem...

    Best Regards
    Gerardo

  • Suggested answer
    YUN ZHU Profile Picture
    95,712 Super User 2025 Season 2 on at
    Hi, hope the following can give you some hints.
    Business Central 2021 wave 2 (BC19): Rounding for base unit of measure (Quantity Rounding Precision)
     
    Thanks.
    ZHU
  • Suggested answer
    Mansi Soni Profile Picture
    8,909 Super User 2025 Season 2 on at
    Hello @xmp,

    The error occurs because the Qty. to Ship field on the Sales Order requires higher precision than what's allowed for the unit of measure. Since your base unit (bag) has a decimal rounding precision of 1, the system doesn't accept fractional values like 0.25 (which represents a partial box). To resolve this, go to the Units of Measure setup for the item, and update the Decimal Rounding Precision for the base unit (bag) to allow smaller values (e.g., 0.01). This will let the system handle conversions like 0.25 boxes (1 bag) without rounding errors.

    Hope this answer will help you to resolve it!

    Regards,
    Mansi Soni
  • Suggested answer
    Sohail Ahmed Profile Picture
    11,148 Super User 2025 Season 2 on at
    This issue happens because the Qty. to Ship on the Sales Order is using the box UOM, which expects whole numbers due to its decimal precision setting. When the pick tries to ship 0.25 boxes, it fails.
     
    To fix this:
     
    Go to Units of Measure for Item A.
     
    For the Box UOM, increase the "Decimal Places" (e.g., from 0 to 2) in the Qty. per Unit of Measure or allow more decimal precision for Qty. to Ship.
     
    Alternatively, always ship in Base Unit (bags) if partial box shipping is needed.
     
     
    ✅ Mark this as the verified answer if helpful.
     
     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,664

#2
YUN ZHU Profile Picture

YUN ZHU 960 Super User 2025 Season 2

#3
Jainam M. Kothari Profile Picture

Jainam M. Kothari 773 Super User 2025 Season 2

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans