To anyone who has been reading this thread......
I've been asked to provide a more complete answer to this from one of my
esteemed colleagues , who shall remain nameless due to his apparent
embarrassment about being confused
So here goes.....
In MXP 8.1d (and 7.4) the invoice.document number is initially set to the
seq-no * -1 (in Direct Billing). In Order Invoicing its set to recid * -1 .
I presume so as to retain an unique status within the invoice file while
processing multiple invoices.
Thus it follows that the inv-jrnl.invoice-no field would retain the same
value until the actual real invoice document number was found at the end of
the invoice commit. Since the value prior to commit is negative, it
follows that it would not fit in the mask of ">>>>>>>9" defined for the
inv-jrnl.invoice-no.
If a user were to ctrl-c at this point, then the transaction would
normally get backed out gracefully. However - in the case of DB and OI
functions, this does not always occur. Some orphan inv-jrnl records have
been known to stick around, creating problems with resetting the OP Item
Journal . The orphan records have a value in the invoice-no field that
does not make sense, until you consider the above.
Hope this has helped you. I would probably block users from using ctrl-c.
Best Regards,
----------------------------------------------------------------------------
-------------
Fiona Sumpton Voice: (416) 505.9864
MXP / Varnet Consultant Fax: (905) 887.6392
Business Systems Re-engineering Email: fionas@idirect.ca
Unionville, Ont.
Have modem, will travel