Skip to main content
Solved

Regenerate Inventory Planning-object reference not set to an instance of an object

  • May 20, 2024 2:06 PM UTC
  • 10 replies
  • 221 views
  • Translate All

dprince
Freshman I

Hello all,

Getting this error after the latest update.

** Exception: Inventory Planning Error processing First Pass Detail. Type = Inventory Planning Requirement. Inventory ID = BLNK-22X64-29- GL. siteID = GST. Plan Date = 4/17/2024. Stock Qty = 880.0000. FP Record ID = 4368. BOM ID = BOM011160. Object reference not set to an instance of an object.

We can delete the BOM entirely but it will just error on the next one.  Here are shots of the trace log.

 

Thoughts?

 

 

Best answer by Debbie Baldwin

@dprince - not a problem :) If you are working with a VAR, you should have them help you to log a support case so that this will get routed through support so that if there is an issue or a bug, it can get routed to the correct team. 

View original

10 replies

Debbie Baldwin
Community Manager
Forum|alt.badge.img+2
  • Acumatica Product Manager
  • May 20, 2024 2:08 PM UTC

@dprince - Please log a support case for this. 

Translate

dprince
Freshman I
  • Author
  • Freshman I
  • May 20, 2024 2:11 PM UTC

I submitted the logs.  Is that what you mean.  Sorry this is my first submission on the boards.

 

Translate

Debbie Baldwin
Community Manager
Forum|alt.badge.img+2
  • Acumatica Product Manager
  • Answer
  • May 20, 2024 2:17 PM UTC

@dprince - not a problem :) If you are working with a VAR, you should have them help you to log a support case so that this will get routed through support so that if there is an issue or a bug, it can get routed to the correct team. 

Translate

dprince
Freshman I
  • Author
  • Freshman I
  • May 20, 2024 2:20 PM UTC

No problem.  Will do. 

Translate

Forum|alt.badge.img
  • Freshman II
  • May 20, 2024 3:12 PM UTC

Do you have any non-stock items in your BOMs? It’s a known issue that was fixed in 23r1 & 23r2

 

 

Translate

dprince
Freshman I
  • Author
  • Freshman I
  • May 20, 2024 3:26 PM UTC

We do not

Translate

  • Freshman I
  • Jul 17, 2024 9:38 AM UTC

Any Updates to this case? Has the problem been solved? And what actions have been processed? Because I think we’ve the same problem.

Translate

dprince
Freshman I
  • Author
  • Freshman I
  • Jul 17, 2024 12:51 PM UTC

Yes we updated to 2023 R2 and the issue was resolved.

Translate

  • Freshman I
  • Jul 17, 2024 1:13 PM UTC

Thanks for the information. Currently we’re working with 2023 R1, then I’ve to wait. And hopefully it’ll work after the update.

Translate

dprince
Freshman I
  • Author
  • Freshman I
  • Jul 17, 2024 1:18 PM UTC

This is our current build:  Build 23.213.0015

Translate