Hans I'd say go for the change to the view entity; we should then
verify that all the code that is using it performs the proper checks
before using GlAccount anf GlAccountClass.
Jacopo
On Jul 20, 2009, at 4:17 AM, Hans Bakker wrote:
Interesting point and sure we should consider this.
I am digging in the accounting module and found the following I need
your advice on.
There is view called AcctgTransAndEntries
this view links mainly the AcctgTrans and AcctgTransEntries together.
However it also links the GlAccountId and the GlAccountClass in the
view, which means if the
It would seem that using _NA_ when the record is made would give you two
advantages.
1) it would let you see all records
2) let you use the _NA_ in searches to see what is not assigned.
Hans Bakker sent the following on 7/19/2009 7:48 AM:
I am digging in the accounting module and found the
, 2009 8:48:20 AM GMT -07:00 US/Canada Mountain
Subject: all accounting specialists please read
I am digging in the accounting module and found the following I need
your advice on.
There is view called AcctgTransAndEntries
this view links mainly the AcctgTrans and AcctgTransEntries together.
However
Bakker mailingl...@antwebsystems.com
To: dev d...@ofbiz.apache.or
Sent: Sunday, July 19, 2009 8:48:20 AM GMT -07:00 US/Canada Mountain
Subject: all accounting specialists please read
I am digging in the accounting module and found the following I need
your advice on.
There is view called
not be there in the transaction.
Vince Clark
vcl...@globalera.com
(303) 493-6723
- Original Message -
From: Hans Bakker mailingl...@antwebsystems.com
To: dev d...@ofbiz.apache.or
Sent: Sunday, July 19, 2009 8:48:20 AM GMT -07:00 US/Canada Mountain
Subject: all accounting specialists please read
Interesting point and sure we should consider this. Still I think that
having a view from which you expect to see all entries...and where it
can happen some are not shownperhaps do both?
On Sun, 2009-07-19 at 09:43 -0700, BJ Freeman wrote:
It would seem that using _NA_ when the record is
