Yes, that is correct, I mis-wrote.
The origin "document" (record is probably a better term) triggers/ causes the transaction and not each entry in the transaction.
-David On Nov 25, 2007, at 1:59 AM, Jacopo Cappellato wrote:
David,after reviewing the AcctgTrans and AcctgTransEntry entity I've noticed that fixedAssetId, inventoryItemId, physicalInventoryId, partyId, roleTypeId, invoiceId, paymentId, finAccountTransId, shipmentId, receiptId, workEffortId are in the AcctgTrans entity, while partyId and productId are defined in the AcctgTransEntry entity.This sounds slightly different from #4 in your notes: > 4. origin "documents" (detail records) are associated with the > transaction entry, and there are structures for this in OFBiz If the data model is correctly defined, it should be:4. origin "documents" (detail records) are associated with the transactionSorry for the many questions, but I'm moving the information from the list to the Wiki page and I want to be sure I understand the design.Thanks, Jacopo David E Jones wrote:Some notes on journals (GlJournal), transactions (AcctgTrans), transaction entries (AcctgTransEntry), etc: 1. they are optional, transactions do not have to be associated with a journal 2. a transaction is not associated with a GL account and does not represent a debit or credit, each entry in a transaction does 3. journals are not meant to be balanced, individual transactions are (checking to see whether or not an entire journal is balanced is simply a matter of seeing if each transaction is balanced 4. origin "documents" (detail records) are associated with the transaction entry, and there are structures for this in OFBiz I think this is mostly a difference in terminology, most of the rest of what you wrote sounds correct to me based on my understanding based on my research and collaboration with others on accounting systems.-David
smime.p7s
Description: S/MIME cryptographic signature
