#4602 Period_ID errors in some accounting facts
A (now 263) production system has been running for about 4 years.
It has 2 Clients with a total of 21092 accounting facts.
Each Fact has a Period_ID. Each Period_ID has a Client_ID so it follows that an Accounting Fact in Client_1 should not have a period_which ID belongs to Client_2.
Client_1 has 15500 Facts of which 60 have a period_ID which belongs to Client_2. Client_1 has 56 Period_IDs and 7 of those periods have trx with the period mismatch error.
Client_2 has 5591 Facts of which 115 have a period_ID which belongs to Client_1. Client_2 has 53 Period_IDs and 4 of those periods have trx with the period mismatch error.
The errors have occurred randomly over time with the most recent occurring in June 2007.
The errors have occurred in tables:
318-invoices
335-payments
735-allocations
I am assuming that the financial report writer functions on balances summarized by period so I assume the above described errors have the possibility of creating incorrect values in financial reports. I have not checked.
I have attached to pdf's which show the pattern of the errors.
This will not be reproducible in GardenWorld!
regards..
Logged In: YES
user_id=1039991
Originator: YES
File Added: client 1000000 period errors.pdf
Logged In: YES
user_id=1039991
Originator: YES
Note that finding each document with a period_id error and "reposting" corrects the period error however users will not want to be reposting all transactions or even reposting individual transactions related to closed years in case something else changes (eg due to product costs, invoices in foreign currencies where additional Currency Rates have been added perhaps in error, etc).
I assume some extra period checking will be required in the code that does the posting?
Can you please provide a sql script that will reset the period_ID explicitly in the accounting fact without reposting the documents.
Logged In: YES
user_id=1039991
Originator: YES
can you please provide some feedback on this...thanks
Logged In: YES
user_id=1893599
Originator: NO
Can you please provide us with more information on the errors. This will help us understand the problem better.
Logged In: YES
user_id=1039991
Originator: YES
I understand that this is now acknowledged as a bug and has been fixed.
see for further info...
http://sourceforge.net/tracker/index.php?func=detail&aid=1820810&group_id=176962&atid=879332
please confirm.
Logged In: YES
user_id=1893599
Originator: NO
Yes, this has been fixed in core. Thanks.