|
Size: 927
Comment:
|
Size: 1347
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 22: | Line 22: |
| On the debtor record, last invoice({{{lastinv}}}) is updated. | On the debtor record, last invoice({{{lastinv}}}) and last payment({{{lastpay}}}) are updated. |
| Line 24: | Line 24: |
| On the creditor record, last transactions({{{last_tran}}}) is updated. | On the creditor record, last transaction({{{last_tran}}}) is updated. Once the program has finished running, {{{recalc_salesa}}} must be run to recalculate the sales analysis. Once that is done, the period end dates in {{{glcont}}}, {{{gencont}}} and {{{pedaad}}} must be updated manually. A reindex,{{{trrein}}}, should be run to reindex by date and by master file. Finally, {{{recalc_salesa}}}, should be run to recalculate the sales analysis. |
Date rolling utility
The utility dateroll can be used to roll the date forwards or backwards in a company.
Currently, the program must be compiled under debug sql mode to run correctly.
%> dateroll -?
Usage:
dateroll [-d numDays|-v] [-?]
-d Specify the number of days to roll transactions
-v Verbose mode
-? Print this help
%> dateroll -d 365 -vIt traverses through the transaction file tran.dat and adds the number of days specified to any non zero dates found. It ignores any transaction with the EXTN flag on it.
The program also goes through the stock record, the debtor record and the creditor record. On the stock record, last movement(lastmov) and last purchase(lpdate) fields are updated.
On the debtor record, last invoice(lastinv) and last payment(lastpay) are updated.
On the creditor record, last transaction(last_tran) is updated.
Once the program has finished running, recalc_salesa must be run to recalculate the sales analysis.
Once that is done, the period end dates in glcont, gencont and pedaad must be updated manually.
A reindex,trrein, should be run to reindex by date and by master file.
Finally, recalc_salesa, should be run to recalculate the sales analysis.