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 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 transaction does not have a GlAccountId or > GlAccountClassId it will not show. > > This 'anomaly' shows most on the invoice transactionlist at the bottom > of the screen, if no glAccountId could be found the transaction is not > listed, but is there. > > so it is proposed that these fields are optional in this view: > - <view-link entity-alias="ATE" rel-entity-alias="GLA"> > + <view-link entity-alias="ATE" rel-entity-alias="GLA" > rel-optional="true"> > <key-map field-name="glAccountId"/> > </view-link> > - <view-link entity-alias="GLA" rel-entity-alias="GLAC"> > + <view-link entity-alias="GLA" rel-entity-alias="GLAC" > rel-optional="true"> > > HOWEVER..... > > This view is used in many places in services. I scanned most of them and > there is often a selection on GlAccount of GlAccountClass so the outcome > should still be the same. > > So can i put in this change? I realize it could have some impact on the > accounting processing and everybody should be aware of this change. > On the other hand every service should get all the entries of a > transaction and not only the ones with a filled account and class... > > Regards, > Hans > -- BJ Freeman http://www.businessesnetwork.com/automation http://bjfreeman.elance.com http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro Systems Integrator.
