Small and medium business | Business Central, N...

Arithmetic operation resulted in an overflow error

(4) Share

Report

Posted on by DP-19051228-0

171

Hello, I have a customer that gets this error when they run the planning worksheet. The error is caused by close to 100 items and it only happens once or twice every few weeks then goes away. We think it could maybe be a circular reference, a calendar problem, or planning parameters that cause this error, but we're not sure. Has anyone ran into a similar issue before? The customer creates a lot of production orders and assembly orders, when the planning worksheet runs correctly it's about 900 lines give or take.

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (7)

Answers (0)

Sort by

Suggested answer

Alex A 3,083 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

The first thing I would suspect is a customization. See if you can find a modification that was done in relation to this process.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 99,324 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

This doesn't seem like a standard function. Try the following method.

Dynamics 365 Business Central: How to check whether the current page/report is standard or customized

https://yzhums.com/41471/

If this is not a standard feature, please contact your partner.

Thanks.

ZHU

Was this reply helpful? Yes No
Dhiren Nagar 2,898 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Can yoy provide call stack to this error? Use Copy details option on the error message.

Regards,

Dhiren.

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 13,323 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello ,

This error is almost always one (or a small set) of items producing “insane” numbers during planning (qty/date bucket math, UoM conversion, reorder modifiers, etc.), and because it depends on the live mix of demand/supply it can show up only sometimes and then “go away.” The quickest way to catch the culprit is to run Calculate Plan with Stop and Show First Error so the run stops on the first failing item, then use the Planning Error Log to jump to the affected item(s) and review their planning/UoM parameters for outliers (huge min/max/reorder qty/order multiple/rounding precision, weird Qty. per Unit, etc.). Microsoft explicitly describes the Stop and Show First Error + Planning Error Log flow for diagnosing planning run errors.

Regards,
Oussama Sabbouh

Was this reply helpful? Yes No
Manish Sharma 101 on at

Like (0)

Report
Copy link

Link copied!

Can you share the error details, see the error popup has share details, click on that and copy the error details.

That might give some information as to if its standard or custom.

Was this reply helpful? Yes No
DP-19051228-0 171 on at

Like (0)

Report
Copy link

Link copied!

Hi all, here's the error message. Thank you for your help

Error message:

Arithmetic operation resulted in an overflow.

Internal session ID:

076178f0-8b73-4c9b-a641-41b1463dc970

Application Insights session ID:

ceb5ab26-5f8f-40f5-a47f-c7521373791e

Client activity id:

344ee7c0-e2c0-4c35-9ef4-d534ebb73594

Time stamp on error:

2026-02-27T14:21:52.6252553Z

AL call stack:

"Inventory Profile Offsetting"(CodeUnit 99000854).MaintainPlanningLine line 20 - Base Application by Microsoft version 27.3.44313.46295

"Inventory Profile Offsetting"(CodeUnit 99000854).ScheduleForward line 3 - Base Application by Microsoft version 27.3.44313.46295

"Inventory Profile Offsetting"(CodeUnit 99000854).CreateSupplyForward line 26 - Base Application by Microsoft version 27.3.44313.46295

"Inventory Profile Offsetting"(CodeUnit 99000854).PlanItem line 151 - Base Application by Microsoft version 27.3.44313.46295

"Inventory Profile Offsetting"(CodeUnit 99000854).CalculatePlanFromWorksheet line 25 - Base Application by Microsoft version 27.3.44313.46295

"Calc. Item Plan - Plan Wksh."(CodeUnit 5431).CalculateAndGetPlanningCompList line 18 - Base Application by Microsoft version 27.3.44313.46295

"Calc. Item Plan - Plan Wksh."(CodeUnit 5431).Code line 26 - Base Application by Microsoft version 27.3.44313.46295

"Calc. Item Plan - Plan Wksh."(CodeUnit 5431).OnRun(Trigger) line 3 - Base Application by Microsoft version 27.3.44313.46295

"Calculate Plan - Plan. Wksh."(Report 99001017)."Item - OnAfterGetRecord"(Trigger) line 20 - Base Application by Microsoft version 27.3.44313.46295

"Planning Worksheet"(Page 99000852)."CalculateRegenerativePlan - OnAction"(Trigger) line 11 - Base Application by Microsoft version 27.3.44313.46295

Was this reply helpful? Yes No
Suggested answer

Dhiren Nagar 2,898 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi,

Can you please check your "Requisition Line" table? Use this link - https://businesscentral.dynamics.com/Sandbox?table=246

In this table, sort descending on "Line No." field. Check the value of "Line No." field.

If it is way bigger, consider deleting that and following other lines. Basically Integer variable as a limit it can go. System is trying to a new Requisition line but when it tries to increase Line No. by 10000, it is going beyond its permitted range and hence this error.

So deleting those lines with Bin Line No. value will resolve the issues. It's better to always clean your Requisition Lines if not in use.

✅ Tick the checkbox below to mark the answer as verified, if it helped resolve your question.

Regards,

Dhiren.

LinkedIn - https://www.linkedin.com/in/ca-dhiren-nagar-5079081b2/

Blog - https://dhirennagar.blogspot.com/

Was this reply helpful? Yes No