Re: [Openledger-developer] invoice class

[Klavs K. <kl...@vs...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I was the one talking about them - and I've just added them to the CVS
(incl. SL 2.4.9 and a README in that folder telling people what it is,
and why it is part of the openledger src).

I currently use the Invoice.pm (which uses InvoiceLines.pm) for building
an invoice (incl. paid info if it's paid) and then I call a PostInvoice
method on a sql-ledger object (also my own - small very small class) and
it postes it to the webinterface (as you all do when you post invoices).
Nothing new there.

My hope is to use that PostInvoice function as a "beginning" for the
perl-api interface. We never got a list of methods needed for the
perlapi, but I'll be starting with the PostInvoice function (which will
take an invoice object as parameter) and for now, I was intending to
build it, so I didn't have to give all that excess info the GUI requires
(ie. internal partnr. for the items, internal partnr. & name of
accounts, number of income acc.no and expense accno for each item and so
on).

I plan to use the real accountnr. (ie. not the internal) and the item's
real model name (as set forth in the Number column for items). This
ofcourse means that if you put something that does not have a unique
match - the postinvoice function will fail with a corresponding
errormessage, as it should.

My reasoning for doing it this way, is that then I don't have to have a
list of internal accountnumbers and other excess info, which only the
accounting system really needs to know for my scripts to use, for
creating invoices (as they do now :( )

Next I'll probably write a function to modify an invoice (ie. for now I
need to modify payment details - ie. which account has an existing
payment been made to etc. but I would like to hear ideas for how mod of
the existing invoice should be done - IMHO you'd post a complete
invoice, and it would use the invoicenr.(which is probably the only
thing that has to be unique in every country, atleast pr. year - this
may be a problem? isn't in my situation though - I have totally unique
invoicenumbers) to know which invoice to modify.

Also I need to enhance the Invoice.pm module, to use PaymentLines
instead of just having room for one row of payment info (anyone feel
like cp'ing InvoiceLines.pm to PaymentLines.pm and renaming a bit ? :)

on 15-02-2005 17:41 Udo Spallek wrote:
| Hello,
|
| in the past someone talked about an invoice class for sql-ledger. Anyone
| know where to find this invoice class if it is already published?
|
| Greetings Udo Spallek
|
|
| -------------------------------------------------------
| SF email is sponsored by - The IT Product Guide
| Read honest & candid reviews on hundreds of IT Products from real users.
| Discover which products truly live up to the hype. Start reading now.
| http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
| _______________________________________________
| Openledger-developer mailing list
| Ope...@li...
| https://lists.sourceforge.net/lists/listinfo/openledger-developer

- --
Regards,
Klavs Klavsen, GSEC - kl...@vs... - http://www.vsen.dk
PGP: 7E063C62/2873 188C 968E 600D D8F8  B8DA 3D3A 0B79 7E06 3C62

"Those who do not understand Unix are condemned to reinvent it, poorly."
~  --Henry Spencer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFCGZL2PToLeX4GPGIRAiQzAJ9B+jls5yuh2jU+D8LgPMsen9EQPwCdEgIJ
SFjytp6EZWpx2yK5jVmdTDo=
=8Lta
-----END PGP SIGNATURE-----