Good morning, All,
For the last few days, I have been investigating an issue with a customer's Opera 3 (VFP) system whereby, in Batch Processing, when progressing a number of documents from Delivery Note to Invoices, the Invoice PDF is generated for all documents, but some documents fuily progress to Invoice, whereas some remain in a half Delivery Note, half Invoice state.
Viewing the customer in SOP Processing shows the document as "Del/I", when it should be "Invoice".
Checking the ihead table, for a partially progressed document, shows that the Invoice date, and number, have been populated, but the document status is still set to "D".
Checking the itran table, on the "A" line only, for a partially progressed document, shows that the Invoice date, number, and quantity haven't been populated, nor the delivered quantity set to zero.
I am currently trying to write a data fix for this, as the partially progessed documents are causing my customer lots of problems, not least that what should be fully invoiced documents are still appearing on the Orders List report, and it is not possible to raise a Credit Note against them.
Rather spookily, a separate customer raised a Ticket, only this morning, stating that when progressing a Delivery Note to Invoice, in SOP Processing, occasionaly the document did not fully progress to an Invoice!!
Neither customer has any bespoke in the SOP/Batch Processing area, and so this leads me to believe that there could be an inherent problem within the document progression function of SOP, and I have informed Pegasus Support of such.
The data fix is my priority, so I have yet to investigate either customer's issue to see if I can determine a pattern to those documents that do not fully progress to Invoice. The data fix is quite complex in that it is necessary to try and determine which records in both ihead, and itran, are genuinely part-delivered, or part-Invoiced, and which should be fully invoiced, but are showing as part-Invoiced.
Has anyone else ever encountered this issue and, if so, was there a resolution, or was it just a case of a data fix? Did you ever establish a pattern?
I would be grateful for any thoughts/views that anyone might have on the above, as it looks as though the issue could be quite widespread, and the data corruption caused has quite significant implications.
Much appreciated
Steve
