before I put my two cents in I have searching the Internet and reading where can I put links like www.ofm.wa.gov/roadmap/modeling/generalledger/general_ledger_best_practices_summary.pdf
[EMAIL PROTECTED] sent the following on 11/25/2007 11:07 AM: > Jacopo > > I can answer for the productId part (I too do not understand having the > partyId). Si, when he does the transaction for an an invoice, puts the > individual InvoiceItems a separate AcctgTransEntry record. Then, you have > only one AcctTrans record and multiple AcctgTransEntry records for the > inventory part (the sales part is a second and separate transaction) of one > invoice. > > More commonly, there is one post for the sum of the inventory items sold. > However, this method offers some flexibility if you want to split up cost of > goods or maybe you have separate inventory accounts for different inventory > types. For that reason, I like it. > > Skip > > > > -----Original Message----- > From: Jacopo Cappellato [mailto:[EMAIL PROTECTED] > Sent: Sunday, November 25, 2007 1:00 AM > To: [email protected] > Subject: Re: [OFBiz] Users - Accounting Extension (GL, etc) Now In Beta > > > 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 transaction > > Sorry 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 >> > > > > >
