Hello,
I have created a handful of custom fields (type read-only) that I have included in operational reports. For example, I have balance due and customer PO fields on the collective invoice form.
There is an issue where, if someone has a customer order that gets invoiced into a collective invoice, but changes their PO, when the collective invoice is first printed off originally, the PO comes up as the updated PO but the balance due is zero, even though the balance due is pulling the open amount. (SELECT OPEN_AMOUNT FROM LEDGER_ITEM_CU_DET_QRY WHERE LEDGER_ITEM_ID= :INVOICE_NO)
When we reprint modified the collective invoice form, the PO gets changed to the old PO value and the balance due field becomes the correct, up to date, value.
Has anyone encountered this before? Does anyone know what the correct approach is? This seems like some history tracking issue that collective invoices and customer statements of accounts encounter (same error on statements). I’ve checked the custom field’s value via a quick report and it pulls the most up to date information (correct PO and correct balance due)
I know this is an odd issue since it encapsulates reporting, custom fields, and invoice/statement history tracking, but any and all advise would be greatly appreciated.
Thanks,
Bryan