Ok, getting back to our discussion: The Close a Fiscal Year that I describe previously has the problem where the copied moves have a different move_id and are therefore disassociated from their invoices so that if we reconcile the payments against them in the new fiscal year the invoices will not get marked paid because we have lost the linkage.
So I have worked on another approach that involves maintaining the account balances across fiscal years, data purging and fiscal year closings. The gist of this approach is that we forget about having the closing processes copy any balances or moves. We treat the entire spectrum of fiscal years as one long sequence of periods and we just close periods as necessary to prevent postings. Of course such an approach is not sustainable if you don't take into account the need to purge old data out of the system otherwise it will grind itself to a halt eventually. So now instead of copying balances and moves during closing what we should do is to have the data purge process copy balances (no moves should be necessary since all transactions should be reconciled by this time) into the next fiscal year after the year that is being purged. So what we have is that the only fiscal year that will have any data in the open period is the oldest fiscal year active in the system. The advantage with this method is that we prevent any problems with copied moves and invoices. The only restriction is that the data purge process only purges the oldest fiscal year and requires that there be no unreconciled moves. Otherwise it should not allow you to purge the until all moves are reconciled for the fiscal year being purged. Here is what it looks like: -------------------- m2f -------------------- -- http://www.openerp.com/forum/viewtopic.php?p=24923#24923 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
