Re: [CK-Ledger-users] accno ...
Status: Beta
Brought to you by:
ckwu
|
From: C K Wu <ck...@ch...> - 2002-05-25 18:49:43
|
Adding fields to the gl table is definitely the best way to go about it.
However, I would suggest generalising the setup a little bit, since the
same feature can be utilized for product line P/L, regional P/L and/or
departmental P/L reporting for commercial organizations. The added
fields could be termed something like, attrib1, attrib2, attrib3 (I think
three attribute fields is about right). The
'defaults' table will carry the captions for these fields. Whenever
these fields are displayed on screen or in report, the caption title will
be extracted from the 'defaults' table. This is how I handle the primary
and secondary tax fields. This way, the same code base can be
implemented in public agencies to handle fund/project accounting,
and in commercial business to handle product line/departmental accounting.
I'll send you a separate email to cover other issues.
Got to catch some zzzzzzz's.
Cheers,
CK
robert del huerto wrote:
> On Saturday 25 May 2002 10:46 am, C K Wu wrote:
> > The account number is fine. Lengthy account code can be a pain in
> > the neck for the person performing the actual journal entry coding/input.
> >
>
> I know it's a pain. But, some people have to use fund and project accounting.
> :( For example, a public agency that is awarded a new grant to complete
> certain new projects. They would need to use the same account numbers they
> already have plus attach a prefix to track the new grant fund and another
> prefix for each of the different projects. They would have to provide
> financial statements for each fund (sometimes per project) and consolidated
> financial statements which include all funds and projects.
>
> I'm wondering if you think it'd be alright for me to add fund and project
> fields to the gl table (instead of the chart table.)
>
> Assuming we keep account numbers the same, we could add fund and project
> accounting by doing this:
>
> $where = " WHERE 1=1 " ;
> if ($fund) {
> $where .= " AND fund = $fund_source";
> if ($project) $where .= " AND project = $project_source";
> }
> if ($from) $where .= " AND transdate >= $from_date ";
> if ($to) $where .= " AND transdate <= $to_date " ;
> if ($source) $where .= " AND lower(source) like lower('%$source%') " ;
> if ($description) $where .= " AND lower(description) like
> lower('%$description%') " ;
> $where = urlencode($where) ;
>
> This would give you fund and fund/project views of the general ledger/journal
> entries. We could probably do something similar in all other modules (I
> haven't taken a look at all the code yet.)
>
> What do u think? Would there be a better way to implement this in the current
> code?
>
> robert
|