When does this field (RcvDtl.Invoiced) get set? I couldn’t find any details about it in the Application Help.
We have many old receipts that are clearly invoiced, but they don’t have that bit flag set. Someone here had tried to create a Received Not Invoiced BAQ that relied on that field but it pulls in a bunch of bogus records because they’re super old and super invoiced, but they still don’t have that field set.
I believe this field is set by default and is coming from Company Configuration.
Modules → Finance → AP → Save Receipts for Invoicing. Database field name is APSyst.SaveReceipts.
Field Help says: “A\P invoice entry sets this to “Yes” when the receipt detail line is invoiced. A value of NO either means that the system was not configured to 'Save Receipts for Invoicing” when the receipt line was created or that it has not yet been invoiced via A/P.
(See RcvHead.SaveForInvoicing, RcvHead.Invoiced)"
Looks like this field was later set to true? and hence these records hang in there.
One thing I have noticed is that if the user alters the invoiced qty and strangly the qty does not honour the UOM our EA UOM is set to no decimal-round up and the user can enter in a fraction of the qty and it changes the total on the inovice.
If they do this then the rcvdtl.OurUnInvcReceiptQty is updated and the standard GRNI report checks to see if this value is > 0 if it is then it shows on the report.