David.Simmonds wrote:Mike, So you plan to have one big table called TR_Set which then refers to 4 other tables - one each for each transaction type. Won't this cause performance issues in a larger multi - user system. Every transaction being written to the database will have the same starting point...
David
On the contrary, I think it will mean improved performance.
Currently our reconciliation and audit reports need to trawl through the source documents to reconcile the GL against the sub-ledgers (inventory, debtors and creditors).
Using the Transaction Set concept, we - as you put it - have a single starting point. This way reconciliation and auditing is a lot simpler. Isolating discrepancies should be as simple as comparing the GL entries against the sub-ledger entries for a given period, then refining down to a particular transaction set or sets.
Of course, the main purpose of Transaction Sets is to eliminate the cause of any such discrepancies - the software should encapsulate all related transactions together, so it should not be possible for imbalances between the GL and the sub-ledgers.