Sage 100

Have a customer on 4.50.3 who installed a new terminal server, causing problems with paperless. That is now fixed but they were trying to update a PO receipt register during all of this. They were now trying to update both a rec. of gds and a rec. of inv. but got the error below stating a PO was being referenced in another receipt register. So they deleted all entries in the rec. of gds but still get the message. I ran the DTR and there was an entry for PO-1196. You see below that the current register is PO-1201. I see entries for 1197 through 1200 in some files and I'm not sure they should still be there, e.g. PO_ReceiptVarianceCalculation and PO_DailyPostingWork. I would suggest deleting ALL receipts and rebuilding,etc. but there are 300 entries in rec. of inv. that I'm sure they will not want to re-enter. Thoughts??

Is this batch entry? Perhaps an orphaned batch with this PO referenced? You would need to look in the MAS_xxx\POXXX table to locate any orphaned batches.

No, they do not use batch entry. I copied the data to a test company and reinitialized the two files mentioned above and the update now proceeds. DTR looks good so I am now copying the live data once again as a backup before I do it in the live company.

Did you look to see if there is a record in the PO_ReceiptReturnMatRqByPO that could be causing it?

Yes @RobertaFerguson there are 141 records. What is that file?

The file that @RobertaFerguson is referencing caused me fits last spring when trying to access a PO. The error that you are seeing would display and we could not open the PO. The advantage we had was that there was nothing in either ROG or ROI. We dfdm that table and deleted the rogue PO line. Take a look for any records referencing an ROG.

Should that file have ANY records in it if all data entry files have posted? This looks to have very old PO numbers in it.

Not exactly sure what the purpose is. I think it is a lock file of sorts to prevent multiple record usage. For this particular issue, I think there were about 10 records.

No, it should be emply if everything is updated. I don't remember what causes stuff to get stuck in there but that is where you can delete the records if needed instead of reinitializing.

Thanks @RobertaFerguson!!

I had the same problems last week. I had to re-init the PO_ReceiptVarianceCalculation file where the PO had not been cleared from a prior receipt.

Reinitializing that file is what worked for me too @MikeBrown. There were 16 records in it which all referenced the non-existent PO registers.

An off topic comment here... Since you mentioned it briefly, is there a whitepaper or KB article describing dealing w/ Paperless on Terminal Servers?