Sage 100

Recent upgrade 4.3 to 4.5 -- customer complains that RMA no longer generating an automatic SO as it used to. Suspect user rights and bumped those up as best I could see. Anyone run into this complaint previously?

This is when a customer has an RMA for a repair. They claim on the shiny new 4.5 upgrade that the SO is not created. I found this and checked - we're configured properly http://infosource.sagesoftwareonline.com/sw_attach/kdb.asp?isresolutionconceptid=509075

Found a Sage KB article which seems to hint at some type of bug if a NOF Invoice Number is used (don't know if that applies here) RMA Entry and RMA Receipts Entry do not create a linked sales order or credit memo when using a Not on File (NOF) invoice number.

This looks like a bug carried over from version 4.4.4

I am assuming you have them on PU3?

Wayne, I ran into something like this earlier this year. I do not remember the exact details, but I believe I determined that in the RA_ReturnDetail file there were records that had ""00"" for the APDivisionNo, but no value for the VendorNo and this was causing the SO not to be created. This particular customer did not have RMA integrated with the PO module. Before they create the next RMA receipts entry, find out what the RMA number is and check out the RA_ReturnDetail file and see if there is a value in the APDivisionNo, but no value for the VendorNo. If so delete the ""00"" from the APDivisionNo. Then have them process the RMA return and generate the transactions and see if the SO is created. If this does not make sense, feel free to give me a call.

John this makes sense - and I do see they have a ""00"" division and no vendor number. I believe this is probably all part of Sage's original problem report that appears to stem from an RA where the invoice number is NA aka Not On File. It's probably dropping in the 00 but not the vendor number (I copied the image above). I am guessing that this issue recurs as they process more RMA's such as this so using DFDM probably isn't a long term solution?

Wayne, on the client I had this problem with the new RMA's did not have the division number show up - it was only on converted ones

I tried this - logged into the file and deleted the Division no (00) -- but we still are getting the same results. I can ask if this is happening on freshly entered RMA's (ie - not converted)

I interpreted that the issue discussed in the KB is where there is a NOF SO invoice number and not releated to the vendor number. I would be interested to see if it is happening on newly created RMA's.

The customer is using NOF (say's N/A) invoices and claims not to be able to insert an invoice. I am curious if they do a return but pick an invoice number if it works.

Customer went in and did an RMA with an invoice # attached. The SO was created like it should have been. This appears to be a carryover bug from 4.4 I'm sure the customer is pleased as punch that they pay a big fee to upgrade to 4.5 -- and inherit a critical bug in RMA.

Thanks for sharing this guys. I'm doing a very sizable upgrade in a few weeks for a heavy RMA client that uses a lot of NOF invoices. This may put the brakes on that.