Skip to main content
Solved

Production Scrapping in 25R2

  • February 11, 2026
  • 3 replies
  • 69 views

Hello, 

We are currently in the process of upgrade from 23R2 to 25R2. In the process, of upgrade we encountered an issue with scrapping on production orders. A case/Bug has been opened with Acumatica. However, we do not have an established timeline for resolution at this time. 

 

Problem:
When performing a scrap on a production operation the Production Order Detail will record the scrap on the operation in which it was performed. However, the scrapped qty will not update in the first operations QTY remaining and QTY to Produce Columns. All upstream operations, from before the scrap action will remain in a “Completed” status. In our production environment, if a scrap occurs, we must start over from Operation ID 0010.

This means, we have completely lost visibility to a production order in the upstream work centers that is starting over in the production process due to scrap. This also means, we lose our Material transactions and labor cost associated to the rework of the product in the upstream work centers.  

 

This poses a serious financial and customer impacting risk to our manufacturing process with ACU 25R2. As our company processes upwards of 1500 production orders per day. This scrap bug also poses a significant risk to “signing off” the cutover upgrade to 25R2. Our Cutover is planned for 2/20/2026.


 

Question the Community and Product team:

  1.  Are there any other business that have a similar workflow?
  2. Have you experience the same issue with production scraps in 25R2?
    1. Have you been able to work with or around these conditions?
    2. How are we expected to maintain visibility of production orders with Scrap performed?
  3. Are their any Manufacturing users planning on upgrading to 25R2?
    1. Would this pose a similar risk to your company?
  4. Is there an Expected Resolution Date to this Issue?

 

 

Thank you,

 

Dylan Wigness

Best answer by dwigness

Hello Chris, 

Our consultancy team, had to unravel the code to determine the root cause and patch a solution before our upgrade to 25R2. 

Currently, we are operating on that patch. I have not seen documentation or dates from ACU on a expected solution in the core platform. 

3 replies

Debbie Baldwin
Community Manager
Forum|alt.badge.img+2
  • Acumatica Product Manager
  • April 8, 2026

@dwigness - since you have opened a case on this. I am assuming you have received a reply from support? 


Chris Hackett
Community Manager
Forum|alt.badge.img
  • Acumatica Community Manager
  • August 4, 2026

Hi ​@dwigness were you able to find a solution? Thank you!


  • Author
  • Freshman II
  • Answer
  • August 5, 2026

Hello Chris, 

Our consultancy team, had to unravel the code to determine the root cause and patch a solution before our upgrade to 25R2. 

Currently, we are operating on that patch. I have not seen documentation or dates from ACU on a expected solution in the core platform.