all accounting specialists please read

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

all accounting specialists please read

hans_bakker
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

--
Antwebsystems.com: Quality OFBiz services for competitive rates

Reply | Threaded
Open this post in threaded view
|

Re: all accounting specialists please read

BJ Freeman
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.

Reply | Threaded
Open this post in threaded view
|

Re: all accounting specialists please read

Vince Clark
In reply to this post by hans_bakker
GlAccountId is a required field in AcctgTransEntry so I don't see how it could not be there in the transaction.

Vince Clark
[hidden email]
(303) 493-6723

----- Original Message -----
From: "Hans Bakker" <[hidden email]>
To: "dev" <[hidden email]
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 "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

--
Antwebsystems.com: Quality OFBiz services for competitive rates

Reply | Threaded
Open this post in threaded view
|

Re: all accounting specialists please read

Sharan-F

Hi

If you think about unposted transactions or transactions that fall into the Error Journal then you can get the case where the GLAccountId isnt included in one or both sides of the accounting transaction.

I think this normally happens because there is missing setup in the GL account defaults showing what the default account should be.

Thanks
Sharan

Vince Clark wrote
GlAccountId is a required field in AcctgTransEntry so I don't see how it could not be there in the transaction.

Vince Clark
vclark@globalera.com
(303) 493-6723

----- Original Message -----
From: "Hans Bakker" <mailinglist@antwebsystems.com>
To: "dev" <dev@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 "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

--
Antwebsystems.com: Quality OFBiz services for competitive rates
Reply | Threaded
Open this post in threaded view
|

Re: all accounting specialists please read

hans_bakker
In reply to this post by Vince Clark
If the system cannot find the GLAccountId it is left null and the record
is put in the error journal.... so it can be null....

Regards,
Hans

On Sun, 2009-07-19 at 17:15 -0500, Vince Clark wrote:

> GlAccountId is a required field in AcctgTransEntry so I don't see how it could not be there in the transaction.
>
> Vince Clark
> [hidden email]
> (303) 493-6723
>
> ----- Original Message -----
> From: "Hans Bakker" <[hidden email]>
> To: "dev" <[hidden email]
> 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 "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
>
--
Antwebsystems.com: Quality OFBiz services for competitive rates

Reply | Threaded
Open this post in threaded view
|

Re: all accounting specialists please read

hans_bakker
In reply to this post by BJ Freeman
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 shown....perhaps do both?

On Sun, 2009-07-19 at 09:43 -0700, BJ Freeman wrote:

> 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
> >
>
--
Antwebsystems.com: Quality OFBiz services for competitive rates

Reply | Threaded
Open this post in threaded view
|

Re: all accounting specialists please read

Jacopo Cappellato-4
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. Still I think that
> having a view from which you expect to see all entries...and where it
> can happen some are not shown....perhaps do both?
>
> On Sun, 2009-07-19 at 09:43 -0700, BJ Freeman wrote:
>> 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
>>>
>>
> --
> Antwebsystems.com: Quality OFBiz services for competitive rates
>