Sage 100

I've encountered something strange in RMA. In both 2013 and 2016, the first receipt against an RMA processes just fine and closes the appropriate line on the RMA. Any subsequent receipts generate the transactions okay but don't update back to the RMA. The lines on the RMA stay open and the quantity received never updates. In 2016, the Generate Transactions step throws an error 65 at sy_openobject.pvc at statement 358 for the RA_ReturnDetail_BUS which may be the culprit but Sage was no help with the issue. Has anyone ran into this before?

I'll check. I have a customer that is new and actively using RMA.

What service update on 2016 ?

I'm seeing it happen with 2016.3, 2017.0 and 2013.9. Sage has been able to duplicate it in their systems so I'm amazed it hasn't been reported before. Poor client is on 2013 and is upgrading but that is going to take months so I'm trying to finagle a work-around that will close the line on the RMA when it is supposed to be closed.

Ugh..or just plain ugly...Sage has no idea how brutal some of these issues can be to an end-user. Buy a module to solve a hard to track issue. Sage breaks module . End-user and consultant now have to clean-up Sage's mess.