Firstly, Thanks for the comments on our tracker problem.
I'm sort of following on the back of Cliff's email yesterday about having to
put through a change request for something that, logically, should be done
differently. We've just moved to 6.0 a few weeks back and after just
getting over our first month end, our finance people discovered a little but
annoying problem. The aged debtor report uses the aging days that were held
in company configuration, not a problem so far but the statements also use
these days and they use them in a different way, they need a zero in the
first days field rather than 30. So each month our accountant has to change
them for the Aged Debtors report and then change them for the statements.
Fantastic logic. Epicor in the U.K. don't seem to hold out much hope that I
can push this through as a bug.
Anyone else come across this problem?
Regards
Martin Horton
I'm sort of following on the back of Cliff's email yesterday about having to
put through a change request for something that, logically, should be done
differently. We've just moved to 6.0 a few weeks back and after just
getting over our first month end, our finance people discovered a little but
annoying problem. The aged debtor report uses the aging days that were held
in company configuration, not a problem so far but the statements also use
these days and they use them in a different way, they need a zero in the
first days field rather than 30. So each month our accountant has to change
them for the Aged Debtors report and then change them for the statements.
Fantastic logic. Epicor in the U.K. don't seem to hold out much hope that I
can push this through as a bug.
Anyone else come across this problem?
Regards
Martin Horton