ck-ledger-users — Mailing list and discussion group for CK-Ledger Users

[CK-Ledger-users] CK-Ledger v.0.0.9.1 released

[C K Wu <ck...@ch...>]

Hello, folks,

I have posted a new release, v.0.0.9.1, of CK-Ledger, at
SourceForge.Net.

Features of the new release include,

1.Eliminate all references to SQL-Ledger as requested by the SQL-Ledger
team.

CK-Ledger (with 9 modules, Ledger Admin, Ledger, Inventory, Service, AP,
AR, PO, SO, Quotation) is modeled on an Open Source accounting software
and runs on top of phpGroupWare.  It provides accounting functionalities
to SMEs & utilizes phpgw to administer accounts/groups.  Installation
Manual for CK-Ledger is available at
http://sourceforge.net/projects/ck-ledger.  Please report errror and
suggestion to the mailing list, ck-...@li....
General history and expected development of CK-Ledger is available at
the mailing list's Archive.

Cheers,
Wu Chiu Kay, aka CK Wu, aka CK (CK is the preferred alias)
Hong Kong

[CK-Ledger-users] Re: Bug ?

[C K Wu <ck...@ch...>]

Hi, Geoff,

I am getting forgetful these days.

In the mean time, to rectify your copy of ck-ledger, change line 46
of class.account.inc.php to,

$link .= ($a[AP_amount]) ? ":AP_amount" : "" ;

I am also sending a copy of this email to
ck-...@li....

Regards,
CK

C K Wu wrote:

> Hi, Geoff,
>
> Yes. It is a bug.  It will be rectified in the release after the next.
>
> Over this weekend, I hope to send out an administrative release,
> which cut away all reference of SQL-Ledger from the CK-Ledger
> code.  I received a specific request from the SQL-Ledger team
> to have this done.  It seems that too many people are writing to
> the SQL-Ledger mailing list enquiring whether SQL-Ledger
> is a pre-requisite for CK-Ledger to run.
>
> Regards,
> CK
>
> admin wrote:
>
>> Hi Ck, Coming to grips with AP and AR - I note for some reason I
>> candelete and reinstate the account ledger flags on every flagexcept
>> AP_amount it will delete but will not reinstate -have I missed
>> something or is it a bug My quick perusal of the code couldn't track
>> the problem Regards Geoff
>

[CK-Ledger-users] Re: ckledger description

[Peter <pe...@he...>]

Thank you for the reply. I live in Sydney, which contains all the money
and culture in Australia, :-), so am interested in Geoff's work. 

CK-Ledger installed ok. I had pgpgw rc2 already running for email on one
site and tts on another site. The only page I looked at was the accounts
payable. Lots of stuff to read on that page. I see you could do with
some help in the multiple update area. I will have only one person
updating the ledger at a time so that is not an immediate need.

I will try out the app over the remainder of April.

Peter

C K Wu wrote:
> 
> Hello Peter,
> 
> Thanks for checking CK-Ledger out.  The answer to your questions are,
> 
> 1    Sourceforge limits application description to 255 chars, so there is not much I can do about this  :-(  .
> 
> 2.    More detail information of CK-Ledger is available from
>     a)    the mailing list, ck-...@li...
>     b)    the Installation Manual (only a few pages long) kept at the Docs Section of http://sourceforge.net/projects/ck-ledger
> 
> 3.    CK-Ledger does not requires SQL-Ledger, but it does need apache+phpgroupware as an underlining middle layer
>         and Postgres or MySQL as the DB engine.
> 
> 4.    CK-Ledger is written in pure PHP.
> 
> 5.    I have been with the IT industry for quite a number of years to know that long term plan with an IT product
>         is very much a shifting target.   However, the mailing list, ck-...@li..., will reflect
>         on the intermediate goals of CK-Ledger and the additional modules being developed.  Actually, I am
>         writing a POS module for the next release of CK-Ledger.
> 
> 6.    Geoff from Australia is testing CK-Ledger and is likely that a sample chart of accounts for Australian companies
>         will be developed in future.
> 
> Just so people have better info on CK-Ledger, I am forwarding this reply to ck-...@li...
> 
> Best Regards,
> CK

[CK-Ledger-users] Re: ckledger description

[C K Wu <ck...@ch...>]

Hello Peter,

Thanks for checking CK-Ledger out.  The answer to your questions are,

1    Sourceforge limits application description to 255 chars, so there is not much I can do about this  :-(  .

2.    More detail information of CK-Ledger is available from
    a)    the mailing list, ck-...@li...
    b)    the Installation Manual (only a few pages long) kept at the Docs Section of http://sourceforge.net/projects/ck-ledger

3.    CK-Ledger does not requires SQL-Ledger, but it does need apache+phpgroupware as an underlining middle layer
        and Postgres or MySQL as the DB engine.

4.    CK-Ledger is written in pure PHP.

5.    I have been with the IT industry for quite a number of years to know that long term plan with an IT product
        is very much a shifting target.   However, the mailing list, ck-...@li..., will reflect
        on the intermediate goals of CK-Ledger and the additional modules being developed.  Actually, I am
        writing a POS module for the next release of CK-Ledger.

6.    Geoff from Australia is testing CK-Ledger and is likely that a sample chart of accounts for Australian companies
        will be developed in future.

Just so people have better info on CK-Ledger, I am forwarding this reply to ck-...@li...

Best Regards,
CK

peter wrote:

> Hello ckwu,
> The CK ledger description paragraph at sourceforge is unclear about the need for SQL Ledger. Does your application replace SQL ledger and add extra function or do people have to install SQL ledger first.
>
> If SQL ledger is required now, what are your long term plans?
>
> I ask because I have PHP running flawlessly at many sites and often have problems installing Perl. A pure PHP application is preferable to a mixed language application.
>
> I think including both answers in to the sourceforge description would attract more interest than the current ambiguous description.

[CK-Ledger-users] Re: Hi CK

[C K Wu <ck...@ch...>]

Hi, Geoff,

I think I've got a partial solution to the Ledger Listing question.
A semaphore type of construct could be created to limit the number
of concurrent users invoking the ledger listing all at the same time.
This should lessen the overall loading of processing concurrent ledger
listing requests.  This concurrent user limit can be controlled via a
program kept
within ledger admin.  Actually, this whole facility can be generalised
to any specific part of CK-Ledger, thus allowing flexibility to ASPs
selling CK-Ledger online access.

However, I am no good at this.  I can still recall my CS300 assignment
to create a terminal communication program via semaphones.  It failed
miserably :-(
At the same time, the phpgw api does not seem to provide function call
on such feature.  You may like to try your hand on this one.  Meanwhile,

I'll try to find some logical ways to restrict the total volume of
transactions
that go through one single ledger listing request.

I've yet to find a solution to the second problems.

By the way, there is some interesting development with time-billing.
You
may like to have a look at a feature request from Michael (mikepb78) [at

ck-ledger's project summary page].

Things are looking good.

Cheers,
CK



geoff wrote:

> Hi CK,No havent lost interest -still think ck-ledger has much more
> potentialthan others - have been overseas for 3-4 weeks - see you have
> version9 which I have just downloaded We now have a reasonable number
> of accounts on the ledger and willstart to use the ap and ac modules
> will giveyou feedback as we progress Have you advanced your thinkingon
> what I see as an essential utilitythat of being able to quickly drill
> down to a individual account from thereports facility Regards Geoff

[CK-Ledger-users] New Release, v.0.0.9, of CK-Ledger

[C K Wu <ck...@ch...>]

Hello, folks,

I have posted a new release, v.0.0.9, of CK-Ledger, at SourceForge.Net.

Features of the new release include,

1.An additional Quotation Module.
2.Conversion of Quotation to Sales Order.
3.New folder names (to avoid phpgroupware navbar sequencing problem).
4.Two new icons.
5.Minor bug fixes.

Please note because of changed folder names, installation procedure has
been updated.

CK-Ledger (with 9 modules, Ledger Admin, Ledger, Inventory, Service, AP,
AR, PO, SO, Quotation) is modelled on SQL-Ledger and runs on top of
phpGroupWare.  It adds to SQL-Ledger by providing additional accounting
features & utilizing phpgw to administer accounts/groups.  Installation
Manual for CK-Ledger is available at
http://sourceforge.net/projects/ck-ledger.  Please report errror and
suggestion to the mailing list, ck-...@li....
General history and expected development of CK-Ledger is available at
the mailing list's Archive.

Cheers,
Wu Chiu Kay, aka CK Wu, aka CK (CK is the preferred alias)
Hong Kong

[CK-Ledger-users] New Release, v.0.0.7, of CK-Ledger

[C K Wu <ck...@ch...>]

Hello, folks,

I have posted a new release, v.0.0.7, of CK-Ledger, at SourceForge.Net.

Features of the new release include,

1.Compatibility with MySQL v.3.23.41. [v.3.23 or above is recommended,
since phpgw seems to have problem working with v.3.22.]
2.Case-insensitive searches (suggested by Geoff of Australia)
3.Display of Unbilled PO (outstanding commitment) / SO (unrealized
revenue) for individual vendor/customer.
4.Minor bug fixes.

As no major errors were reported since the last release, I am upgrading
the project to alpha.

To afford MySQL compatibility, temporary tables are used extensively.
As a result,a fair amount of dead table cleansing is required if the
system somehow bombs out.  With MySQL 4.0 supporting UNION statement, I
expect most of these temporary tables will become unnecessary when
MySQL4.0 is formally released.

CK-Ledger (with 8 modules, Ledger Admin, Ledger, Inventory, Service, AP,
AR, PO, SO) is a port of SQL-Ledger running on top of phpGroupWare.  It
adds to SQL-Ledger by providing additional accounting features &
utilizing phpgw to administer accounts/groups.  Installation Manual for
CK-Ledger is available at http://sourceforge.net/projects/ck-ledger.
Please report errror and suggestion to the mailing list,
ck-...@li....  General history and expected
development of CK-Ledger is available at the mailing list's Archive.

Cheers,
Wu Chiu Kay, aka CK Wu, aka CK (CK is the preferred alias)
Hong Kong

[Fwd: [CK-Ledger-users] GL changes from ledger listing]

[C K Wu <ck...@ch...>]

C K Wu wrote:

> Hi, Geoff,
>
> Please send me the modified ledgerlisting.tpl and ledgerlisting.php.
> I'll check and incorporate the changes in the next release.
>
> Thanks for the effort.
>
> I am working on making CK-Ledger to be MySQL compatible.
> I think the next release should have a fair number of new features.
>
> Best Regards,
> CK
>
>
> geoff wrote:
>
>> I have incorporated a couple of changes in the Ledgermodule -
>> specifically to files ledgerlisting.tpl and ledgerlisting.phpto
>> allow amedments to be made from the ledger listing report.When
>> hunting entry errors in the GL it saves considerable time. I dont
>> believe the this list allows file attachments, but would be happy
>> toforward the changes if anybody is interested.
>

[CK-Ledger-users] GL changes from ledger listing

[geoff <ge...@qu...>]

I have incorporated a couple of changes in the Ledger
module - specifically to files ledgerlisting.tpl and ledgerlisting.php=20
to allow amedments to be made from the ledger listing report.=20
When hunting entry errors in the GL it saves considerable time.

I dont believe the this list allows file attachments, but would be happy =
to
forward the changes if anybody is interested.

[CK-Ledger-users] Re: Porting of SQL-Ledger to run on top of phpgroupware

[C K Wu <ck...@ch...>]

Hi, Brian,

I'll check this out too.

Cheers,
CK

Brian Johnson wrote:

> I don't know if this will help - I haven't used pg_dump before
>
> I think this is a dump of all the timetrack tables from phpgroupware
>
> You might be able to use this to set up the timetrack module tables
>
> -----Original Message-----
> From: C K Wu [mailto:ck...@ch...]
> Sent: Monday, February 18, 2002 8:28 PM
> To: Brian Johnson; ck-...@li...
> Subject: Re: Porting of SQL-Ledger to run on top of phpgroupware
>
> Hello, Brian,
>
> Thanks for checking out CK-Ledger.  Nice to hear that the
> software is useful in an actual business setting.
>
> Brian Johnson wrote:
>
> > Awesome idea!
> >
> > This has a lot of potential and thanks for all the work already done.
> >
> > I have a couple of feature requests:
> >
> > 1. could the main contact/company info be the phpgroupware addressbook?
> It
> > would be great if there was one contact database.  It seems logical that
> the
> > main phpgw addressbook should be the one used.  This would allow the
> > reduction of duplication of identical information and therefore
> optimization
> > of the database
> >
>
> This is definitely the way to go.  However, there was discussion on a major
> overhaul of phpgroupware's addressbook/Infolog around June last year with
> the possibility of adding a CRM module.  I would probably wait until the
> formal release of phpgroupware 0.9.14 before working on the integration.
>
> >
> > 2. could we integrate it with a time tracking utility to allow users to
> > input time and charge it based on time spent (I'm in a service industry
> > where we bill based on time).  I have modified the timetrack module to
> work
> > this way - I could send you the code.  It allows users to create a project
> > linked to a contact in the addressbook and then enter time for each
> project.
> > Currently, I set a billout rate for each employee so that we can track it
> > against budget figures but there is no method for invoicing.  The
> automatic
> > linking of this time info to your ledger package for billing and payment
> > tracking would be ideal.  Unfortunately, the service module currently
> would
> > require us to summarize the time info and manually create invoices
> >
> > I'm desperately looking for a replacement to Quickbooks Pro and your
> package
> > seems like a potential winner!  You may be surprised to note that despite
> > the large numbers of SME that bill based on time (pretty much all
> > consultants), there are hardly any accounting packages that can handle
> their
> > needs.  Quickbooks Pro is about the only one, and it still has definite
> > problems.
> >
> > I'm not a programmer, but I can do a bit of php coding modification and I
> > certainly can help you layout a program flow algorithym prior to
> > programming.
>
> Please, do send me the code.  This is exactly what I envisage to be the
> benefit
> of porting SQL-Ledger over to phpgroupware.  Please also send me your
> program
> flow algorithm, especially if it fit with your business' manual billing
> workflow.
>
> By the way, if you find any major error with CK-Ledger-0.0.5, do give me
> a yell.  I am planning to upgrade the project from pre-alpha to alpha.
>
> Best Regards,
> CK
>
>   ------------------------------------------------------------------------
>                   Name: ttrack.dump
>    ttrack.dump    Type: unspecified type (application/octet-stream)
>               Encoding: quoted-printable

[CK-Ledger-users] Re: Porting of SQL-Ledger to run on top of phpgroupware

[C K Wu <ck...@ch...>]

Hi, Brian,

I'll check it out and see how to integrate it with CK-Ledger.

Cheers,
CK

Brian Johnson wrote:

> Here's the timetrack module that we modified
>
> I've forgotten what state we left it in since it didn't do a clean install
> when we first got it but I think we left it pretty clean
>
> Extract the files into a diretory called timetrack below your phpgroupware
> directory
>
> You will likely have to run the sql scripts in the setup/sql directory
>
> It is also important that you create TTrack_Managers and TTrack_Payroll user
> groups and add yourself to them
>
> I'll help you set it up on your system if you run into problems. I'm going
> to try to figure out pgdump so that it will be easier to set up the tables
> in postgresql
>
> I'll forward a summary of the way I think a time billing system should sork
> from a services industry perspective in the near future
>
> -----Original Message-----
> From: C K Wu [mailto:ck...@ch...]
> Sent: Monday, February 18, 2002 8:28 PM
> To: Brian Johnson; ck-...@li...
> Subject: Re: Porting of SQL-Ledger to run on top of phpgroupware
>
> Hello, Brian,
>
> Thanks for checking out CK-Ledger.  Nice to hear that the
> software is useful in an actual business setting.
>
> Brian Johnson wrote:
>
> > Awesome idea!
> >
> > This has a lot of potential and thanks for all the work already done.
> >
> > I have a couple of feature requests:
> >
> > 1. could the main contact/company info be the phpgroupware addressbook?
> It
> > would be great if there was one contact database.  It seems logical that
> the
> > main phpgw addressbook should be the one used.  This would allow the
> > reduction of duplication of identical information and therefore
> optimization
> > of the database
> >
>
> This is definitely the way to go.  However, there was discussion on a major
> overhaul of phpgroupware's addressbook/Infolog around June last year with
> the possibility of adding a CRM module.  I would probably wait until the
> formal release of phpgroupware 0.9.14 before working on the integration.
>
> >
> > 2. could we integrate it with a time tracking utility to allow users to
> > input time and charge it based on time spent (I'm in a service industry
> > where we bill based on time).  I have modified the timetrack module to
> work
> > this way - I could send you the code.  It allows users to create a project
> > linked to a contact in the addressbook and then enter time for each
> project.
> > Currently, I set a billout rate for each employee so that we can track it
> > against budget figures but there is no method for invoicing.  The
> automatic
> > linking of this time info to your ledger package for billing and payment
> > tracking would be ideal.  Unfortunately, the service module currently
> would
> > require us to summarize the time info and manually create invoices
> >
> > I'm desperately looking for a replacement to Quickbooks Pro and your
> package
> > seems like a potential winner!  You may be surprised to note that despite
> > the large numbers of SME that bill based on time (pretty much all
> > consultants), there are hardly any accounting packages that can handle
> their
> > needs.  Quickbooks Pro is about the only one, and it still has definite
> > problems.
> >
> > I'm not a programmer, but I can do a bit of php coding modification and I
> > certainly can help you layout a program flow algorithym prior to
> > programming.
>
> Please, do send me the code.  This is exactly what I envisage to be the
> benefit
> of porting SQL-Ledger over to phpgroupware.  Please also send me your
> program
> flow algorithm, especially if it fit with your business' manual billing
> workflow.
>
> By the way, if you find any major error with CK-Ledger-0.0.5, do give me
> a yell.  I am planning to upgrade the project from pre-alpha to alpha.
>
> Best Regards,
> CK
>
>   ------------------------------------------------------------------------
>                     Name: timetrack.zip
>    timetrack.zip    Type: Zip Compressed Data (application/x-zip-compressed)
>                 Encoding: base64

[CK-Ledger-users] Australian Requirements and other wish list things

[geoff <ge...@qu...>]

In response to some of your questions in relation to Australian requirements

Yes you are correct there is a requirement for
capital and non capital GST -

Taxpayers are given the opportunity to run either
cash or accrual systems - the exact treatment of
your example problem I will have to research

In working through general ledger and trying to correct
an entry - 2 additions I feel will make life much easier

-Include the item amount in the ledger 'search' journal reports
-have a link from each item in the ledger 'listing' report directly to the
edit function of that item

[CK-Ledger-users] Re: CK-Ledger

[C K Wu <ck...@ch...>]

Hi, Geoff,

Yes.  Please channel your suggestions through the mailing list
so everyone has an idea of what new features can be expected.

I have completed the Installation Manual and put it online.
I have also tested a RedFlag Linux install using a remote
Postgresql Server and it works.

The case insensitive search will be in the next release.  Turn out
it is pretty easy to implement.  Just change all the LIKEs to ILIKEs.
The only concern is future MySQL compatibility.  But, MySQL may
well support ILIKE in the future  :-) .

I remember distinctly that there were 3 querys raised when
applying SQL-Ledger to Australian accounting.

1.    Separate recording of tax received and paid including tax rate.
        This should have been solved in CK-Ledger.

2.    Capital vs non-capital GST tax.  This should also have been solved

        with two different types of tax allowed per invoice/po/so
transaction.
        However, you may like to provide for the capital GST and
non-capital
        GST accounts and rates in the sample Australian Chart of
Account.
        You may also like to check if there is a need for a third level
of tax.

3.    Cash-based vs non-cash-based GST tax.  Dieter mentioned that
cash-based
        tax was provided in SQL-Ledger v.1.8.  However, I have a bit of
query as
        to the logical setup.  Say, if there are two outstanding
invoices,

        Jan-01-1995        invoice 00001
A$110.00        (tax A$10.00)
        Jan-01-2002        invoice 00002
A$1100.00           (tax A$100.00)

        The customer sends in a cheque for A$1100 saying that he/she has
problem
        with invoice 00001, and is not going to pay it.  Does the
Australian Tax Authority
        requires that tax accrued on older transactions be settled
first, or is it up to the
        tax payer to decide. If you could check this out, I could
perhaps make cash-based
        tax accounting available two or three release down the road.

Oh.  I think someone mentioned a Business Activity Statement required by
the Australian
Tax Authority.  It is perhaps also something to be added to the
Australian side of CK-Ledger.

And, no hurry.  Take your time.  I have a really long wish list for
CK-Ledger myself.

Cheers,
CK



admin wrote:

> Hi CK Putting a few of our own accounts into CK - ledgerAt first look,
> very few incompatibilities to Australianrequirements. Australia has
> one goods and services tax (GST) currentlyat 10% The 'Add New Jounal'
> Button I think would be better named'Add Journal Entry' As with SQL-
> Ledger it would be really nice to have theaccount major headings
> outlined in the drop down accountlist. Only working through general
> ledger at this stage - will keepsending comments as they come to
> me (would you prefer me to go through the users mailing
> list) Regards Geoff

[CK-Ledger-users] [Fwd: Re: Outstanding Effort]

[C K Wu <ck...@ch...>]

-------- Original Message --------
   Subject: Re: Outstanding Effort
      Date: Mon, 18 Feb 2002 20:43:43 +0800
      From: C K Wu <ck...@ch...>
        To: geoff <ge...@qu...>
References: <005a01c1b86f$77bb0370$c4ec2acb@geoff>

Hi, Geoff,

Glad to hear your problem's solved.

If you don't mind, I like to forward our last few email correspondence
to
ck-...@li..., so others (especially Debian
users)
knows what to watch out for.

At the moment, I am writing up an installation manual to be placed at
sourceforge.net.  Obviously, my first email at the ck-ledger-users
mailing
list missed out on a very important point about the installation
process.
Meanwhile, could you do me a little favour and email me your Debian,
Apache,
PostgreSQL and phpGroupware configuration so I can incorporate
it in the installation manual.

And, if you feel like it, you may like to help along with the coding
especially in two areas,

1.    Providing an Australian Chart of Accounts
2.    Coding the (taxation return) reports  required by the Australian
Taxation Authority.

..../ledadmin/adminbuild.php is the program that provides the default
chart.
You may like to have a look at it to see the amount of afford needed.
Well,
actually, the coding is simple.  The problem is actually finding the
typical
Chart of Account of an Australian Company.

Best Regards
CK


geoff wrote:

> Hi CK, CK - ledger is truly an outstanding effort of yours-After
> creating that table - everything workingas advertised. I have only had
> time to have a brief look at CK-ledgerbut everything appears to be
> operating - I am trulyimpressed with your effort and believe that
> CK-ledgerwill surpass sql-ledger - if for nothing else but the easeof
> installation for the less technical user ,the additionalfeatures
> incorporated in groupware and the largephp user base. As I work
> through it, I would be pleased to offer myhumble opinions on
> intuitiveness ,application to the Australian accounting requirements,
> or any bugs I trip across. Looking forward to future correspondence
> Geoff

[CK-Ledger-users] [Fwd: Outstanding Effort]

[C K Wu <ck...@ch...>]

-------- Original Message --------
Subject: Outstanding Effort
   Date: Mon, 18 Feb 2002 19:25:34 +1100
   From: "geoff" <ge...@qu...>
     To: "C K Wu" <ck...@ch...>

Hi CK, CK - ledger is truly an outstanding effort of yours-After
creating that table - everything workingas advertised. I have only had
time to have a brief look at CK-ledgerbut everything appears to be
operating - I am trulyimpressed with your effort and believe that
CK-ledgerwill surpass sql-ledger - if for nothing else but the easeof
installation for the less technical user ,the additionalfeatures
incorporated in groupware and the largephp user base. As I work through
it, I would be pleased to offer myhumble opinions on intuitiveness
,application to the Australian accounting requirements, or any bugs I
trip across. Looking forward to future correspondence Geoff

[CK-Ledger-users] [Fwd: Re: Minor problem]

[C K Wu <ck...@ch...>]

-------- Original Message --------
   Subject: Re: Minor problem
      Date: Mon, 18 Feb 2002 13:17:25 +0800
      From: C K Wu <ck...@ch...>
        To: admin <ad...@qu...>
References: <002401c1b792$9f0b4a30$c4ec2acb@geoff>
            <3C6...@ch...>
            <004d01c1b7fb$8cb4fbb0$c4ec2acb@geoff>

Geoff,

No bother.  It is this kind of process that allows Open Source Software
to be
tested and experience accumulated.

Obviously, I have not tested phpgroupware and ck-ledger in a Debian
environment.
However, I have been able to re-trace your steps in RedHat7.2 and get
the exact
error message that you mentioned in your last email.

I performed a quick fix by creating the tables required by
phpgroupware's inventory
module manually and subsequently was able to access ledadmin and ar
normally.

Table creation steps:
# su -l postgres
$ psql phpgroupware
$ \i /var/www/html/phpgroupware/inv/doc/create_tables.pgsql

and if Debian support this, it could be done via a single command,
# su -l -c "psql phpgroupware <
/var/www/html/phpgroupware/inv/doc/create_tables.pgsql"

You may need to check and find out the exact path for
[phpgroupware base directory]/inv/doc/create_tables.pgsql in your
machine.

See if this works for your case.  Whatever's the outcome, please give me
a reply.
Would like to follow thru' and see how things go.

Best Regards,
CK


admin wrote:

>  Sorry CK should have been a little more explicit Debian and postgres
> 7.0 groupware 0.9.12 Install groupware - no errors calendar
> /admin/etc working ( but no phpgw_inv_statuslist table in DB) Untar
> ck-ledger modules to same directory level as groupware modules
> -install ledadmin and ar (didnt botherwith the whole 8 until I
> determined I could get to ledadmin)through groupware admin. Create new
> user with permissionto access both ) Into phpgroupware as new user -
> both icons visible (ledadmin and ar) error occurs on clicking either
> icon.Which I guess you would expect seeing the table is notthere and
> there has been nothing done to change tabledata from initial install.
> I guess the question is - should that table be created onevery
> groupware install regardless of subsequent applications and if so why
> wasnt it - have i missed somesubtlety in the groupware install and why
> do other essentialgroupware tables appear to be in place except this
> one. Certainly appreciate your effort and if I hadn't spent a
> daylooking for clues wouldn't ask. Regards Geoff
>
>      ----- Original Message -----
>      From:C K Wu
>      To: admin
>      Sent: 17 February, 2002 10:50 PM
>      Subject: Re: Minor problem
>       Hi, Geoff,
>
>      This is an error coming from phpgw's api module, and is
>      probably caused
>      by some unreported/logical error occurring prior to entering
>      the api module.
>
>      So, just to clarify,
>
>      1.    Were you able to see the eight abacus icons in the
>      navbar?
>      2.    Were you able to see the welcome page of ledadmin ?
>      3.    Were you able to see the welcome page of the other 7
>      modules ?
>      4.    If the answer to Q.2 is yes, when did the error pop up
>      ?
>
>      a.    After you clicked Admin/Setup choice at the top left
>      hand corner ?
>      b.    After choosing action 4 -- Delete all data and data
>      tables ?
>      c.    After choosing action 1 -- Setup Data Table ?
>      d.    After choosing Build Chart of Accounts and other
>      Master Data ?
>      e.    After choosing Create Test Data ?
>
>      If you could provide the info above, it will be clearer
>      where the hidden
>      error is.  [Could be a programming error in the code itself
>      : (   ]
>      I'll go jogging now.  Be back in an hour.
>
>      Oh.  By the way.  phpgw_inv_statuslist is a table used by
>      the phpgw's
>      native inventory module.  It should be created during
>      phpgw's setup
>      process.  I have it appearing in a clean phpgw 0.9.14RC1
>      install.
>      You may like to check if you have accidentally activated
>      phpgw's
>      native inventory module, which is included in subdirectory
>      named "inv"
>      as opposed to CK-Ledger's which is housed in a subdirectory
>      named
>      "inventory".
>
>      Best Regards,
>      CK
>
>
>
>      admin wrote:
>
>     > Hi,After using sql-ledger but developing in php not
>     > perlwas interested in giving ck-ledger a run.Not using
>     > phpgroupware before I now have it workingas advertised
>     > with postgres. After going through the install procedure
>     > for new applicationsI run up against this error when
>     > initiating ledadmin from groupware Warning: PostgreSQL
>     > query failed: ERROR: Relation 'phpgw_inv_statuslist' does
>     > not exist in
>     > /var/www/phpgroupware/phpgwapi/inc/class.db_pgsql.inc.php
>     > on line 96
>     > Database error: Invalid SQL: select * from
>     > phpgw_inv_statuslist
>     > PostgreSQL Error: 1 (ERROR: Relation
>     > 'phpgw_inv_statuslist' does not exist )This table
>     > definitely does not exist A little baffled - if you have
>     > the time and its shortand easy would appreciatea a
>     > leadRegards Geoff
>

[CK-Ledger-users] [Fwd: Re: Minor problem]

[C K Wu <ck...@ch...>]

-------- Original Message --------
   Subject: Re: Minor problem
      Date: Mon, 18 Feb 2002 08:39:15 +1100
      From: "admin" <ad...@qu...>
        To: "C K Wu" <ck...@ch...>
References: <002401c1b792$9f0b4a30$c4ec2acb@geoff>
            <3C6...@ch...>

 Sorry CK should have been a little more explicit Debian and postgres
7.0 groupware 0.9.12 Install groupware - no errors calendar  /admin/etc
working ( but no phpgw_inv_statuslist table in DB) Untar ck-ledger
modules to same directory level as groupware modules -install ledadmin
and ar (didnt botherwith the whole 8 until I determined I could get to
ledadmin)through groupware admin. Create new user with permissionto
access both ) Into phpgroupware as new user - both icons visible
(ledadmin and ar) error occurs on clicking either icon.Which I guess you
would expect seeing the table is notthere and there has been nothing
done to change tabledata from initial install. I guess the question is -
should that table be created onevery groupware install regardless of
subsequent applications and if so why wasnt it - have i missed
somesubtlety in the groupware install and why do other
essentialgroupware tables appear to be in place except this
one. Certainly appreciate your effort and if I hadn't spent a daylooking
for clues wouldn't ask. Regards Geoff

     ----- Original Message -----
     From: C K Wu
     To: admin
     Sent: 17 February, 2002 10:50 PM
     Subject: Re: Minor problem
      Hi, Geoff,

     This is an error coming from phpgw's api module, and is
     probably caused
     by some unreported/logical error occurring prior to entering
     the api module.

     So, just to clarify,

     1.    Were you able to see the eight abacus icons in the
     navbar?
     2.    Were you able to see the welcome page of ledadmin ?
     3.    Were you able to see the welcome page of the other 7
     modules ?
     4.    If the answer to Q.2 is yes, when did the error pop up ?

     a.    After you clicked Admin/Setup choice at the top left
     hand corner ?
     b.    After choosing action 4 -- Delete all data and data
     tables ?
     c.    After choosing action 1 -- Setup Data Table ?
     d.    After choosing Build Chart of Accounts and other Master
     Data ?
     e.    After choosing Create Test Data ?

     If you could provide the info above, it will be clearer where
     the hidden
     error is.  [Could be a programming error in the code itself  :
     (   ]
     I'll go jogging now.  Be back in an hour.

     Oh.  By the way.  phpgw_inv_statuslist is a table used by the
     phpgw's
     native inventory module.  It should be created during phpgw's
     setup
     process.  I have it appearing in a clean phpgw 0.9.14RC1
     install.
     You may like to check if you have accidentally activated
     phpgw's
     native inventory module, which is included in subdirectory
     named "inv"
     as opposed to CK-Ledger's which is housed in a subdirectory
     named
     "inventory".

     Best Regards,
     CK



     admin wrote:

    >  Hi, After using sql-ledger but developing in php not perlwas
    >  interested in giving ck-ledger a run. Not using phpgroupware
    >  before I now have it workingas advertised with postgres.
    >  After going through the install procedure for new
    >  applicationsI run up against this error when initiating
    >  ledadmin from groupware Warning: PostgreSQL query failed:
    >  ERROR: Relation 'phpgw_inv_statuslist' does not exist in
    >  /var/www/phpgroupware/phpgwapi/inc/class.db_pgsql.inc.php on
    >  line 96
    >  Database error: Invalid SQL: select * from
    >  phpgw_inv_statuslist
    >  PostgreSQL Error: 1 (ERROR: Relation 'phpgw_inv_statuslist'
    >  does not exist )This table definitely does not exist A
    >  little baffled - if you have the time and its shortand easy
    >  would appreciatea a lead Regards Geoff

[CK-Ledger-users] [Fwd: Re: Minor problem]

[C K Wu <ck...@ch...>]

-------- Original Message --------
   Subject: Re: Minor problem
      Date: Sun, 17 Feb 2002 19:50:37 +0800
      From: C K Wu <ck...@ch...>
        To: admin <ad...@qu...>
References: <002401c1b792$9f0b4a30$c4ec2acb@geoff>

Hi, Geoff,

This is an error coming from phpgw's api module, and is probably caused
by some unreported/logical error occurring prior to entering the api
module.

So, just to clarify,

1.    Were you able to see the eight abacus icons in the navbar?
2.    Were you able to see the welcome page of ledadmin ?
3.    Were you able to see the welcome page of the other 7 modules ?
4.    If the answer to Q.2 is yes, when did the error pop up ?

a.    After you clicked Admin/Setup choice at the top left hand corner ?

b.    After choosing action 4 -- Delete all data and data tables ?
c.    After choosing action 1 -- Setup Data Table ?
d.    After choosing Build Chart of Accounts and other Master Data ?
e.    After choosing Create Test Data ?

If you could provide the info above, it will be clearer where the hidden

error is.  [Could be a programming error in the code itself  : (   ]
I'll go jogging now.  Be back in an hour.

Oh.  By the way.  phpgw_inv_statuslist is a table used by the phpgw's
native inventory module.  It should be created during phpgw's setup
process.  I have it appearing in a clean phpgw 0.9.14RC1 install.
You may like to check if you have accidentally activated phpgw's
native inventory module, which is included in subdirectory named "inv"
as opposed to CK-Ledger's which is housed in a subdirectory named
"inventory".

Best Regards,
CK



admin wrote:

> Hi, After using sql-ledger but developing in php not perlwas
> interested in giving ck-ledger a run. Not using phpgroupware before I
> now have it workingas advertised with postgres. After going through
> the install procedure for new applicationsI run up against this error
> when initiating ledadmin from groupware Warning: PostgreSQL query
> failed: ERROR: Relation 'phpgw_inv_statuslist' does not exist in
> /var/www/phpgroupware/phpgwapi/inc/class.db_pgsql.inc.php on line 96
> Database error: Invalid SQL: select * from phpgw_inv_statuslist
> PostgreSQL Error: 1 (ERROR: Relation 'phpgw_inv_statuslist' does not
> exist )This table definitely does not exist A little baffled - if you
> have the time and its shortand easy would appreciatea a lead Regards
> Geoff

[CK-Ledger-users] [Fwd: Minor problem]

[C K Wu <ck...@ch...>]

-------- Original Message --------
Subject: Minor problem
   Date: Sun, 17 Feb 2002 20:08:09 +1100
   From: "admin" <ad...@qu...>
     To: <ck...@ch...>

Hi, After using sql-ledger but developing in php not perlwas interested
in giving ck-ledger a run. Not using phpgroupware before I now have it
workingas advertised with postgres. After going through the install
procedure for new applicationsI run up against this error when
initiating ledadmin from groupware Warning: PostgreSQL query failed:
ERROR: Relation 'phpgw_inv_statuslist' does not exist in
/var/www/phpgroupware/phpgwapi/inc/class.db_pgsql.inc.php on line 96
Database error: Invalid SQL: select * from phpgw_inv_statuslist
PostgreSQL Error: 1 (ERROR: Relation 'phpgw_inv_statuslist' does not
exist )This table definitely does not exist A little baffled - if you
have the time and its shortand easy would appreciatea a lead Regards
Geoff

[CK-Ledger-users] Re: Outstanding Effort

[C K Wu <ck...@ch...>]

Geoff,

Thanks for pitching in.  There are also some feedback
from Canadia with some enhancement requests.  You may
like to have a look at ck-...@li....

The two "Done" buttons thing is actually my lazy programmer's
trick.  I was actually reusing a generic confirming template
which normally have a "Yes" and a "No" button.  Re-using
the template helps to minimise the number of dedicated templates.

By the way, I am planning to upgrade the project to alpha soon.

Best Regards,
CK

geoff wrote:

>  CK - only to pleased to assist as time permits I would like to
> initially work through and put up some ofour own accounts - The new
> user viewpoint is agood one for picking up errors. My brief look to
> date as follows 1. Notes field in table tax missing - have replaced
> (char(255)).2. Suggest searches be not capital sensitive3. two 'Done'
> buttons on many pages. Will get the other info to you when I can stamp
> outa few customers grass fires. (Our Company Quixl P/L does ISP - web
> hosting - web design etc) Regards geoff
>
>      ----- Original Message -----
>      From: C K Wu
>      To: geoff
>      Sent: 18 February, 2002 11:43 PM
>      Subject: Re: Outstanding Effort
>       Hi, Geoff,
>
>      Glad to hear your problem's solved.
>
>      If you don't mind, I like to forward our last few email
>      correspondence to
>      ck-...@li..., so others (especially
>      Debian users)
>      knows what to watch out for.
>
>      At the moment, I am writing up an installation manual to be
>      placed at
>      sourceforge.net.  Obviously, my first email at the
>      ck-ledger-users mailing
>      list missed out on a very important point about the
>      installation process.
>      Meanwhile, could you do me a little favour and email me your
>      Debian, Apache,
>      PostgreSQL and phpGroupware configuration so I can
>      incorporate
>      it in the installation manual.
>
>      And, if you feel like it, you may like to help along with
>      the coding especially in two areas,
>
>      1.    Providing an Australian Chart of Accounts
>      2.    Coding the (taxation return) reports  required by the
>      Australian Taxation Authority.
>
>      ..../ledadmin/adminbuild.php is the program that provides
>      the default chart.
>      You may like to have a look at it to see the amount of
>      afford needed.  Well,
>      actually, the coding is simple.  The problem is actually
>      finding the typical
>      Chart of Account of an Australian Company.
>
>      Best Regards
>      CK
>
>
>      geoff wrote:
>
>     > Hi CK, CK - ledger is truly an outstanding effort of
>     > yours-After creating that table - everything workingas
>     > advertised. I have only had time to have a brief look at
>     > CK-ledgerbut everything appears to be operating - I am
>     > trulyimpressed with your effort and believe that
>     > CK-ledgerwill surpass sql-ledger - if for nothing else but
>     > the easeof installation for the less technical user ,the
>     > additionalfeatures incorporated in groupware and the
>     > largephp user base. As I work through it, I would be
>     > pleased to offer myhumble opinions on intuitiveness
>     > ,application to the Australian accounting requirements, or
>     > any bugs I trip across. Looking forward to future
>     > correspondence Geoff
>

[CK-Ledger-users] Re: Porting of SQL-Ledger to run on top of phpgroupware

[C K Wu <ck...@ch...>]

Hello, Brian,

Thanks for checking out CK-Ledger.  Nice to hear that the
software is useful in an actual business setting.

Brian Johnson wrote:

> Awesome idea!
>
> This has a lot of potential and thanks for all the work already done.
>
> I have a couple of feature requests:
>
> 1. could the main contact/company info be the phpgroupware addressbook?  It
> would be great if there was one contact database.  It seems logical that the
> main phpgw addressbook should be the one used.  This would allow the
> reduction of duplication of identical information and therefore optimization
> of the database
>

This is definitely the way to go.  However, there was discussion on a major
overhaul of phpgroupware's addressbook/Infolog around June last year with
the possibility of adding a CRM module.  I would probably wait until the
formal release of phpgroupware 0.9.14 before working on the integration.

>
> 2. could we integrate it with a time tracking utility to allow users to
> input time and charge it based on time spent (I'm in a service industry
> where we bill based on time).  I have modified the timetrack module to work
> this way - I could send you the code.  It allows users to create a project
> linked to a contact in the addressbook and then enter time for each project.
> Currently, I set a billout rate for each employee so that we can track it
> against budget figures but there is no method for invoicing.  The automatic
> linking of this time info to your ledger package for billing and payment
> tracking would be ideal.  Unfortunately, the service module currently would
> require us to summarize the time info and manually create invoices
>
> I'm desperately looking for a replacement to Quickbooks Pro and your package
> seems like a potential winner!  You may be surprised to note that despite
> the large numbers of SME that bill based on time (pretty much all
> consultants), there are hardly any accounting packages that can handle their
> needs.  Quickbooks Pro is about the only one, and it still has definite
> problems.
>
> I'm not a programmer, but I can do a bit of php coding modification and I
> certainly can help you layout a program flow algorithym prior to
> programming.

Please, do send me the code.  This is exactly what I envisage to be the benefit
of porting SQL-Ledger over to phpgroupware.  Please also send me your program
flow algorithm, especially if it fit with your business' manual billing
workflow.

By the way, if you find any major error with CK-Ledger-0.0.5, do give me
a yell.  I am planning to upgrade the project from pre-alpha to alpha.

Best Regards,
CK

[CK-Ledger-users] Re: CK-Ledger v.0.0.5 released

[C K Wu <ck...@ch...>]

Hi, everybody again,

I am afraid the installation procedure that I wrote in my last email
missed out on a major point.  Geoff from Australia, went thru' a
(phpgroupware 0.9.12+ck-ledger) installation on his Debian machine
and got stuck at step 21.  After choosing the LedgerAdmin icon, he
got the following errors,

Warning: PostgreSQL query failed: ERROR: Relation 'phpgw_inv_statuslist'
does not exist in
/var/www/phpgroupware/phpgwapi/inc/class.db_pgsql.inc.php on line 96
Database error: Invalid SQL: select * from phpgw_inv_statuslist
PostgreSQL Error: 1 (ERROR: Relation 'phpgw_inv_statuslist' does not exist )

The problem was solved by manually creating the table,
'phpgw_inv_statuslist', through,

# su -l postgres
$ psql phpgroupware
$ \i /var/www/html/phpgroupware/inv/doc/create_tables.pgsql

or using a single command,
# su -l -c "psql phpgroupware <
/var/www/html/phpgroupware/inv/doc/create_tables.pgsql"

After that, everything went normal.  Therefore, the installation procedure
should have an additional Step 6a,

# su -l -c "psql phpgroupware <
/var/www/html/phpgroupware/inv/doc/create_tables.pgsql"

Apparently, with phpgroupware 0.9.14RC1, the table was created by
phpgroupware's own setup process.

Best Regards,
CK


C K Wu wrote:

> Hi, everybody,
>
> I have uploaded the tarball for a pre-alpha release version, 0.0.5, of
> CK-Ledger to sourceforge yesterday.
>
> As indicated in the release note, it is modeled on SQL-Ledger v.1.8.2.
> It require phpgroupware 0.9.12, but will also work with 0.9.14RC1.
>
> Features additional to SQL-Ledger are,
> Ledger Admin - data backup/restore;
> Ledger (G/L) - audit control report, journal history, ledger listing;
> Inventory - audit control report, inventory in/out history, explicit
> inventory adjustment transaction, goods receipt transaction, goods
> delivery transaction;
> Service - separate module for access by non-warehouse staff;
> Accounts Payable - audit control report, manual override of system
> calculated tax, separate rate and account setting for tax received and
> paid, explicit payment transaction, matching of payment against invoice
> allowing one payment settling multiple invoices, invoice/PO matching,
> invoice payment history, cheque printing;
> Accounts Receivable - audit control report, manual override of system
> calculated tax, separate rate and account setting for tax received and
> paid, explicit receipt transaction, matching of receipt against invoice
> allowing one receipt settling multiple invoices, invoice/SO matching,
> invoice receipt history, customer statement, invoice reminder, official
> receipt;
> Purchase Order - audit control report, purchase order billing history;
> Sales Order - audit control report, sales order billing history.
>
> Working Configuration:
> RedHat7.2, Apache 1.3.20, PostgreSQL 7.1.3, phpgroupware 0.9.12 (most
> stable setup)
> RedHat7.2, Apache 1.3.20, PostgreSQL 7.1.3, phpgroupware 0.9.14RC1 (some
> errors occur when logging out of phpgw, but this does not affect the
> working of CK-Ledger)
> Mandrake 8.1, Apache 1.3.20, PostgreSQL 7.1.2, phpgroupware 0.9.14RC1
> (same errors as with RedHat 7.2)
>
> [I have also tried RedFlag Linux Server 2.0.  It used to work before I
> set up the Ledger Admin module.  It fails at the Ledger Admin/Ledger
> Build process.
> Apparently, it's due to the use of a new SQL syntax not supported by the
> PostgreSQL v.6.x.  If PostgreSQL is upgraded to 7.1.2 or above, it would
> probably work.  If anyone is successful in this regard or is able to run
> CK-Ledger with RedFlag Linux Server 3.0, would appreciate a note back to
> this mailing list.]
>
> If anyone is successful with other Linux distribution, would also
> appreciate a note back to this list.
>
> Installation Procedure.
> 1.    Setup a working Linux environment with Apache and PostgreSQL fully
> installed.
> 2.    Setup phpgroupware 0.9.12 or 0.9.14RC1.  For detail instruction,
> please refer to www.phpgroupware.org
> 3.    Test to ensure you have a working phpgroupware setup.
> 4.    Download ck-ledger-0.0.5.tar.gz from sourceforge.net.
> 5.    # cd /var/www/html/phpgroupware                    [assuming
> /var/www/html/phpgroupware is phpgw's base directory]
> 6.    # tar -xzvf <path of ck-ledger-0.0.5.tar.gz>        [extract code
> into 8 folders, ledadmin, ledger, inventory, service, ap, ar, po, so
> within phpgw's base directory]
> 7.    Login phpgroupware as administrator.
> 8.    Invoke admin (the castle icon) module.
> 9.    Pick the "Applications" choice
> 10.    Repeat the following process 8 times (ie. Step 11, 12a, 11, 12b,
> 11, 12c, ..........).
> 11.    Press "Add" button
> 12.    Fill in the new application details
> a.        Application name:  ledadmin    Application title: Ledger
> Administration ;   [leave the other settings unchanged];  Press "Add"
> button
> b.        Application name:  ledger        Application title:
> Ledger;                            [leave the other settings
> unchanged];  Press "Add" button
> c.        Application name:  inventory    Application title:
> CK-inventory                    [leave the other settings unchanged];
> Press "Add" button
> d.        Application name: service        Application title:
> Service                            [leave the other settings
> unchanged];  Press "Add" button
> e.        Application name: ap                Application title:
> Accounts Payable            [leave the other settings unchanged];  Press
> "Add" button
> f.        Application name: ar                Application title:
> Accounts Receivable        [leave the other settings unchanged];  Press
> "Add" button
> g.        Application name: po                Application title:
> Purchase Order               [leave the other settings unchanged]; Press
> "Add" button
> h.        Application name: so                Application title:  Sales
> Order                    [leave the other settings unchanged];  Press
> "Add" button
> 13.    Invoke admin (the castle icon) module again.
> 14.    Pick the "User groups" choice
> 15.    Click "Edit" on the Default group line            [This is just
> an example.  You could create your own group and work from there too]
> 16.    Click to activate the modules, Ledger Administration, Ledger,
> CK-inventory, Service, Accounts Payable, Accounts Receivable, Purchase
> Order, Sales Order
> 17.    Press "Submit Changes" button.
> 18.    Logout from adminstrator account.
> 19.    Login as a common member of the Default group, say demo.
> 20.    The CK-Ledger modules will show up as "abacus" icons.
> 21.    Choose the LedgerAdmin module.  You may have to click all 8 icons
> to find out which icon relates to which module.
> 22.    Read in detail the "Welcome to LedgerAdmin" page.
> 23.    Pick Admin/Setup choice at the top left hand corner
> 24.    Choose action 4 - Delete all Data and Data Tables
> 25.    Press "Input Admin Action Parameters" button
> 26.    Press "Start Action" button                        [For new
> installs, there may be error messages saying that the data tables are
> not present.  But don't worry]
> 27.    Press one of the "Done" buttons
> 28.    Choose action 1 - Setup Data Tables
> 29.    Press "Input Admin Action Parameters" button
> 30.    Press "Start Action"
> button                                              [A list of table
> created message will appear]
> 31.    Press one of the "Done" buttons
> 32.    Choose action 2 - Build Chart of Accounts and other Master Data
> 33.    Press "Input Admin Action Parameters" button
> 34.    Pick your desired Chart of Account                    [Currently,
> only Default Chart of Account works.  It is modelled on SQL-Ledger's
> default chart]
> 35.    Presss "Start Action" button
> 36.    Press one of the "Done" buttons
> 37.    Choose action 3 - Create Test Data                    [For live
> production, creation of test data should be skipped]
> 38.    Press "Input Admin Action Parameters" button
> 39.    Press "Start Action"
> 40.    Press one of the "Done" buttons
>
> At this point, CK-Ledger is fully functional and all features are
> available for your testing.
>
> A few points to note:
>
> 1.    Some of the menu choices are still not yet implemented
> 2.    There is an inventory module native to phpgroupware, therefore it
> is advisable to name CK-Ledger's inventory as CK-inventory.
> 3.    The cheque printing facility assumes a normal stub-based manual
> handwriting cheque format (not the special computer stationery type).
>         The layout would have to be tuned for different bank's cheque
> format.  The included facility is just for sample only.
> 4.    Since this is a pre-alpha release, so DO NOT, DON'T, DO NOT AGAIN
> use this version against any production data or environment.
>
> Have a nice time testing this version.  Please report any error back to
> this list.
>
> Best Regards,
> Wu, Chiu Kay aka CK Wu aka CK (CK is the preferred alias)
> Hong Kong

[CK-Ledger-users] Re: Porting of SQL-Ledger to run on top of phpgroupware

[C K Wu <ck...@ch...>]

Todd,

Thank you for the information.

Last year, when I started the porting effort, I did look into ebXML to
find the best way to augment such a port.  However, at the time, ebXML
was apparently majoring on the interchange of ledger-processed results or
intermediate results, which was probably not what SQL-Ledger or CK-Ledger
intended, ie, internal use within an SME.  But, I'll certainly look into the
current situation of ebXML.  Given the current development with the
Enron case, there may yet be a more fundamental change with the underlining
accounting classification, so there may be another round of ebXML
modifications.

With the other standards, as you mentioned, they seem to be still in a state of
flux.
At this point, I would rather go for the traditional way of developing an
application
by adding more useful basic functions or by integrating discrete systems to add

value for the end user.

IMHO, standards are good.  However, too many layers of standards will
have the effect of stopping new developers from entering the game, as the
new guys have to expertise themselves with all these standards and its
complex interplay before they can start to service or develop
standard-compliant
systems.  Perhaps, the Open Source Movement, in a small way, helps
new comers to experiment with new ways beyond established standards.

Best Regards,
CK


Todd Boyle wrote:

> CK, thank you for the work you're doing. I'd like to advocate your
> work be based on a public standards process.
>
> The need for common semantics in design of accounting
> systems includes naming of tables and fields, making it
> unambiguous exactly what is the meaning of information stored
> in the application.  The precise definitions of these things by design,
> can greatly improve the efficiency of integrators when they come later,
> to connect other applications.  And it can greatly improve the
> quality of their results.   ISO 11179 or ebXML metadata registries
> are today, the prevailing way of documenting the naming of
> information entities and the meanings and relations between
> them.  This is your foundation for mapping.  The latest release
> of ebXML Core Components Technical Specification was
> announced and posted as an attachment, in the mailing list at
>   http://lists.ebtwg.org/archives/ebtwg-ccs/200202/msg00089.html
>
> Common semantics also includes the naming and definition
> of behaviors, i.e. the interfaces that the other object can
> expect to be performed when they are invoked.   UML modeling
> is today, the prevailing way of documenting, and communicating
> these behaviors.  There are at least three free UML programs now,
> (Objecteering, Poseidon and ArgoUML)
>
> There is a bigger picture within which these semantic arguments
> are being discussed and that is, the semantics used EXTERNALLY
> between trading partners.  The prevailing external vocabulary today
> is EDI of course.  But due to its shortcomings an explosion of
> XML vocabularies have come into use in hundreds of domains.
> The converging of these into a single framework is happening
> in a number of competing Mega-Standards bodies who are in the
> business of creating lots of different standards as their business
> model (ISO, W3C, DISA/X12, UN/CEFACT, OASIS, the OMG, etc.)
>
> I just want to point out a resource for you, for significant General Ledger
> standards at http://www.arapxml.net/research.htm  and the ongoing
> work on an ARAP general ledger on that site.  Please join with
> us to make the ARAP spec into something that serves your
> needs as well as everybody elses, and build against that.   Further,
> I hope you will join in the standardization of a wider set of GL
> information entities described in the Requirements document
> on the same website,
> http://www.arapxml.net/requirements.htm
>
> Thanks for your patience,
> TOdd
> Todd Boyle CPA  9745-128th Ave NE  Kirkland WA
> International Accounting Services, LLC  www.gldialtone.com
> tb...@ro...  425-827-3107  project www.arapxml.net
>
> At 10:52 PM 2/15/02, C K Wu wrote:
> >Hello, folks,
> >
> >This is a rather lengthy post.  Please bear with me.
> >
> >I have started a project at sourceforge and named it, CK-Ledger, which
> >is a port of SQL-Ledger to
> >phpgroupware.  http://sourceforge.net/projects/ck-ledger

[CK-Ledger-users] Porting of SQL-Ledger to run on top of phpgroupware

[C K Wu <ck...@ch...>]

Hello, folks,

This is a rather lengthy post.  Please bear with me.

I have started a project at sourceforge and named it, CK-Ledger, which
is a port of SQL-Ledger to phpgroupware.  Before I go any further, I
like to congratulate Dieter Simader and the SQL-Ledger team in
developing an excellent open source solution.

Since CK-Ledger is based on SQL-Ledger, its functionalities are very
similar to SQL-Ledger's.  The features that I have added, include,

LedgerAdmin =96 data backup/restore;
Ledger =96 audit control report, account journal history, ledger listing;
Inventory =96 audit control report, inventory in/out history, explicit
inventory adjustment transaction, goods receipt transaction, good
delivery transaction;
Service =96 separate module for access by non-warehouse staff;
Accounts Payable =96 audit control report, manual override of system
calculated tax, separate rate and account setting for tax received and
paid, explicit payment transaction, matching of payment against invoice
allowing one payment settling multiple invoices, invoice/PO matching,
invoice payment history, cheque printing;
Accounts Receivable =96 audit control report, manual override of system
calculated tax, separate rate and account setting for tax received and
paid, explicit receipt transaction, matching of receipt against invoice
allowing one receipt settling multiple invoices, invoice/SO matching,
invoice receipt history, customer statement, invoice reminder, official
receipt;
Purchase Order =96 audit control report, purchase order billing history;
Sales Order =96 audit control report, sales order billing history, order
acknowledgement;

However, there are SQL-Ledger features that I have not (or not yet)
implemented, notably standalone AP/AR transactions and foreign currency
translation.  At the same time, the internal data structure of CK-Ledger
and SQL-Ledger are different.

Most transactions are provided with standard search, add, view copy and
delete facilities.  Journal reversing feature is included.  While
currently, here in Hong Kong, we do not charge a transactional tax (in
the form of sales or VAT tax), such tax is being contemplated.
Therefore, I have produced, 2 streams, to handle invoices, POs and SOs
that do and do not carry tax.

CK-Ledger is structured as 8 phpgroupware modules, LedgerAdmin, Ledger,
Inventory, Service, AccountsPayable, AccountsReceivable, PurchaseOrder
and SalesOrder.  Each of these modules can be set up as visible or
hidden from specific user (group) utilizing phpgroupware's native
grouping and admin functions.

Please, be warned that the current version, v.0.0.5, is a half-baked
edition of a pre-alpha version, so DON'T and I repeat, DON'T, apply this
version in any production environment.  For one thing, the rounding and
presentation of tax calculation results have not been sufficiently
stress tested.  However, I did test this version against the following
configuration without any major error:

RedHat 7.2, Apache 1.3.20, PostgreSQL 7.1.3, phpgroupware 0.9.12 (most
stable setup)
RedHat 7.2, Apache 1.3.20, PostgreSQL 7.1.3, phpgroupware 0.9.14RC1
(Some errors occurred when logging out of phpgroupware, but this would
not affect the working of CK-Ledger)
Mandrake 8.1, Apache 1.3.20, PostgreSQL 7.1.2, phpgroupware 0.9.14RC1
(Same errors as with RedHat 7.2)

To test drive CK-Ledger, download the tarball from sourceforge.net.
Expand the tarball into 8 folders (ledadmin, ledger, inventory, service,
ap, ar, po, so) within the phpgroupware directory.  Login as
phpgroupware administrator to enable individually the 8 modules.  [To
avoid confusion with phpgroupware's native inventory module, you may
like to name CK-Ledger's inventory module, as something like,
CK-Inventory.]  Invoke LedgerAdmin and create test data as indicated in
the index page.  I have also posted the detail installation procedure at
ck-...@li....  Please report any error you
found to ck-...@li..., I'll gladly rectify any
error as soon as possible.

I have not applied for CK-Ledger to be included under phpgroupware
because,

1.Currently, it only work with PostgreSQL.  Back when I started the
software porting, MySQL was still being criticised for =93not supporting
transactions=94
2.I don't intend to make CK-Ledger compatible with fee charging database
engines, ie Oracle, MSSQL, Sybase, etc, although I am OCP(Oracle8) and
MCDBA certified.
3.Currently, CK-Ledger definitely fails some of phpgroupware's coding
standards.
4.The protracted discussion over =93gif=94 is too much a drag for me.  I =
am
not a political puritan by any standard.
5.I have not even started to consider php3 compatibility.  CK-Ledger is
developed using php-4.0.6.

If you are wondering why I did the software porting in the first place,
here are the reasons,

1.I am fully unemployed at the moment, so may as well use the spare
time.
2.My backgrounds are LPIC-1, OCP(AD, Order Fulfillment, Procurement),
MCSE, MCDBA, MCSD, FHKSA, CISA, so when I saw Antonio Gallardo's email
back in Jan-2001 suggesting integration of SQL-Ledger and phpgroupware,
it was too tempting to pass over.

My immediate plan is to produce a simplified/traditional Chinese version
of CK-Ledger for use in the Greater China region (PRC, Hong Kong, Macau,
Taiwan) and, at the same time, work on an hr and payroll extension for
CK-Ledger and to better integrate CK-Ledger with phpgroupware.  I'll
probably create a Setup3 compliant version when phpgroupware 0.9.14 is
formally released.

I would like to appeal for assistance from other developers in the
Greater China region in helping to produce the Chinese version of
CK-Ledger, especially in terms of the format of reports required by the
local taxation authority when reporting VAT received and recovery
claimed.

At the same time, assistance from other phpgroupware developers is most
welcome.  Comparing to phpgroupware developers, I am definitely email
novice.  While CK-Ledger does implement auto emailing of invoice,
statement, order acknowledgement to customer, and purchase order to
vendor, such features are rather rudimentary.  The only audit trail of
having a email sent is a bcc back to the sender's email address.  It
would be nice to have copy of the email auto dropped into invoice_sent,
statement_sent, po_sent (etc) folders within the phpgroupware
environment, or dropped into a customer/vendor specific folder.  With
direct emailing of purchase order to vendor, the email could be a
primary piece of legal evidence on the T&Cs of goods/service provision.
Thus, whether the email has been sent/received and the timing of the
email posting/receipt could have  major legal implications.  It would be
nice to have options to sent receipt-requesting email, to auto-attach
electronic signature or to have the email sent via SSL, etc, etc, etc.
Again it would be nice to have the various documents auto-faxed instead
of being emailed.  I have actually tried html2ps+gs+efax and
successively faxed out but the resulting fax was simply too ugly.  All
these features are beyond me, so your assistance, in any form, is most
welcome and will be acknowledged.  The importance of such features is
evidenced by a SQL-Ledger user indicating his/her main use of SQL-Ledger
was to automate the sending of invoices.  Other phpgroupware module
developers integrating his/her module with CK-Ledger, eg time billing,
would also be most welcome.

Assistance from MySQL developers to ensure CK-Ledger works with MySQL
will also be highly appreciated.  For one thing, I am sure the Data
Restore routine will not work with MySQL, because I am getting lazy and
simply use a PostgreSQL command, =93psql=94, to facilitate the data resto=
re.

Currently, there is only one default template.  Both idsociety and
verdilak are empty.  Developers with an artistic touch are welcome to
fill in the missing templates or to provide other new templates.

While contributions will be graciously acknowledged in the index page of
each module, I don't like to go into political arguments as to how major
a contribution should be, before it is acknowledged, so you will have to
trust me on deciding who and what to acknowledge.

Come to think about it.  If some folks would consolidate phpgroupware's
file handling capability, add in the ability to manipulate
OpenOffice/KOffice docs, CAD (QCAD, SuperMap, AutoCAD, Microstation)
files, etc, to produce a Document Management System within phpgroupware,
then phpgroupware would probably become phpCorporateWare with phpgw
consultants everywhere.

This is my HK$0.02 contribution towards phpgroupware v.1.0.

Have a nice, happy and perhaps belated Chinese New Year (be you Chinese
or not),
Wu Chiu Kay aka CK Wu aka CK (CK is the preferred alias)
Hong Kong

[CK-Ledger-users] CK-Ledger v.0.0.5 released

[C K Wu <ck...@ch...>]

Hi, everybody,

I have uploaded the tarball for a pre-alpha release version, 0.0.5, of
CK-Ledger to sourceforge yesterday.

As indicated in the release note, it is modeled on SQL-Ledger v.1.8.2.
It require phpgroupware 0.9.12, but will also work with 0.9.14RC1.

Features additional to SQL-Ledger are,
Ledger Admin - data backup/restore;
Ledger (G/L) - audit control report, journal history, ledger listing;
Inventory - audit control report, inventory in/out history, explicit
inventory adjustment transaction, goods receipt transaction, goods
delivery transaction;
Service - separate module for access by non-warehouse staff;
Accounts Payable - audit control report, manual override of system
calculated tax, separate rate and account setting for tax received and
paid, explicit payment transaction, matching of payment against invoice
allowing one payment settling multiple invoices, invoice/PO matching,
invoice payment history, cheque printing;
Accounts Receivable - audit control report, manual override of system
calculated tax, separate rate and account setting for tax received and
paid, explicit receipt transaction, matching of receipt against invoice
allowing one receipt settling multiple invoices, invoice/SO matching,
invoice receipt history, customer statement, invoice reminder, official
receipt;
Purchase Order - audit control report, purchase order billing history;
Sales Order - audit control report, sales order billing history.

Working Configuration:
RedHat7.2, Apache 1.3.20, PostgreSQL 7.1.3, phpgroupware 0.9.12 (most
stable setup)
RedHat7.2, Apache 1.3.20, PostgreSQL 7.1.3, phpgroupware 0.9.14RC1 (some
errors occur when logging out of phpgw, but this does not affect the
working of CK-Ledger)
Mandrake 8.1, Apache 1.3.20, PostgreSQL 7.1.2, phpgroupware 0.9.14RC1
(same errors as with RedHat 7.2)

[I have also tried RedFlag Linux Server 2.0.  It used to work before I
set up the Ledger Admin module.  It fails at the Ledger Admin/Ledger
Build process.
Apparently, it's due to the use of a new SQL syntax not supported by the
PostgreSQL v.6.x.  If PostgreSQL is upgraded to 7.1.2 or above, it would
probably work.  If anyone is successful in this regard or is able to run
CK-Ledger with RedFlag Linux Server 3.0, would appreciate a note back to
this mailing list.]

If anyone is successful with other Linux distribution, would also
appreciate a note back to this list.

Installation Procedure.
1.    Setup a working Linux environment with Apache and PostgreSQL fully
installed.
2.    Setup phpgroupware 0.9.12 or 0.9.14RC1.  For detail instruction,
please refer to www.phpgroupware.org
3.    Test to ensure you have a working phpgroupware setup.
4.    Download ck-ledger-0.0.5.tar.gz from sourceforge.net.
5.    # cd /var/www/html/phpgroupware                    [assuming
/var/www/html/phpgroupware is phpgw's base directory]
6.    # tar -xzvf <path of ck-ledger-0.0.5.tar.gz>        [extract code
into 8 folders, ledadmin, ledger, inventory, service, ap, ar, po, so
within phpgw's base directory]
7.    Login phpgroupware as administrator.
8.    Invoke admin (the castle icon) module.
9.    Pick the "Applications" choice
10.    Repeat the following process 8 times (ie. Step 11, 12a, 11, 12b,
11, 12c, ..........).
11.    Press "Add" button
12.    Fill in the new application details
a.        Application name:  ledadmin    Application title: Ledger
Administration ;   [leave the other settings unchanged];  Press "Add"
button
b.        Application name:  ledger        Application title:
Ledger;                            [leave the other settings
unchanged];  Press "Add" button
c.        Application name:  inventory    Application title:
CK-inventory                    [leave the other settings unchanged];
Press "Add" button
d.        Application name: service        Application title:
Service                            [leave the other settings
unchanged];  Press "Add" button
e.        Application name: ap                Application title:
Accounts Payable            [leave the other settings unchanged];  Press
"Add" button
f.        Application name: ar                Application title:
Accounts Receivable        [leave the other settings unchanged];  Press
"Add" button
g.        Application name: po                Application title:
Purchase Order               [leave the other settings unchanged]; Press
"Add" button
h.        Application name: so                Application title:  Sales
Order                    [leave the other settings unchanged];  Press
"Add" button
13.    Invoke admin (the castle icon) module again.
14.    Pick the "User groups" choice
15.    Click "Edit" on the Default group line            [This is just
an example.  You could create your own group and work from there too]
16.    Click to activate the modules, Ledger Administration, Ledger,
CK-inventory, Service, Accounts Payable, Accounts Receivable, Purchase
Order, Sales Order
17.    Press "Submit Changes" button.
18.    Logout from adminstrator account.
19.    Login as a common member of the Default group, say demo.
20.    The CK-Ledger modules will show up as "abacus" icons.
21.    Choose the LedgerAdmin module.  You may have to click all 8 icons
to find out which icon relates to which module.
22.    Read in detail the "Welcome to LedgerAdmin" page.
23.    Pick Admin/Setup choice at the top left hand corner
24.    Choose action 4 - Delete all Data and Data Tables
25.    Press "Input Admin Action Parameters" button
26.    Press "Start Action" button                        [For new
installs, there may be error messages saying that the data tables are
not present.  But don't worry]
27.    Press one of the "Done" buttons
28.    Choose action 1 - Setup Data Tables
29.    Press "Input Admin Action Parameters" button
30.    Press "Start Action"
button                                              [A list of table
created message will appear]
31.    Press one of the "Done" buttons
32.    Choose action 2 - Build Chart of Accounts and other Master Data
33.    Press "Input Admin Action Parameters" button
34.    Pick your desired Chart of Account                    [Currently,
only Default Chart of Account works.  It is modelled on SQL-Ledger's
default chart]
35.    Presss "Start Action" button
36.    Press one of the "Done" buttons
37.    Choose action 3 - Create Test Data                    [For live
production, creation of test data should be skipped]
38.    Press "Input Admin Action Parameters" button
39.    Press "Start Action"
40.    Press one of the "Done" buttons

At this point, CK-Ledger is fully functional and all features are
available for your testing.

A few points to note:

1.    Some of the menu choices are still not yet implemented
2.    There is an inventory module native to phpgroupware, therefore it
is advisable to name CK-Ledger's inventory as CK-inventory.
3.    The cheque printing facility assumes a normal stub-based manual
handwriting cheque format (not the special computer stationery type).
        The layout would have to be tuned for different bank's cheque
format.  The included facility is just for sample only.
4.    Since this is a pre-alpha release, so DO NOT, DON'T, DO NOT AGAIN
use this version against any production data or environment.

Have a nice time testing this version.  Please report any error back to
this list.

Best Regards,
Wu, Chiu Kay aka CK Wu aka CK (CK is the preferred alias)
Hong Kong