openledger-developer Mailing List for OpenLedger (Page 7)
Brought to you by:
klavs
Menu
▾
▴
openledger-developer — Developer list for discussing SL3 development
You can subscribe to this list here.
| 2005 |
Jan
|
Feb
(15) |
Mar
(83) |
Apr
(23) |
May
(10) |
Jun
(6) |
Jul
(14) |
Aug
(5) |
Sep
(1) |
Oct
(7) |
Nov
(6) |
Dec
(1) |
|---|
|
From: Michael L. <ml...@da...> - 2005-03-02 18:53:06
|
> One of you talked about having recorded which SQL queries were done for
> the different actions - I could use a list of SQL queries it runs, when
> posting a new general ledger transaction - to doublecheck.
>
I believe I was the one that mentioned that. To configure you server to
log all SQL statements to the log file modify postgres.conf. Look for
the line:
#log_statement = 'none'
and change it to:
log_statement = 'all'
> I'd be happy to hear if any of you have any design ideas? or if you just
> like my idea :)
>
> Also - if we could identify some tasks that we each would like to work
> on (usually because we need to use them ourselves) - that way we can
> create a list of tasks, and who they are assigned to?
> - --
After several months of distractions I have begun looking at the
CGI-Formbuilder and Template-Toolkit perl modules as possible solutions
to separating the API layer from presentation layer. Has anyone had
experience with these?
--Mike
|
|
From: Klavs K. <kl...@vs...> - 2005-03-02 18:48:03
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 s/transaction function/post_transaction function/ :) Also I can't see why his post_transaction funtion does so many selects, when posting a transaction (AFAIK) only touches two tables - gl and acc_trans. I must be missing something. In my head, you'd just insert in the gl table - get the assigned ID, and use that when posting the transactionlines (that'll be another object just as InvoiceLines I guess ;) I'd be very happy if you could tell me what I'm missing? It does ofcourse save the employee ID of the user who posted it. What should we do with that - just let it be parameter to the postTransaction function? Or should we build a login scheme of some sort for the API (seems a bit hmm.. to me)? on 02-03-2005 19:16 Klavs Klavsen wrote: | Hi guys, | | I'm looking at SL code -and I think I'll build the API "transaction" | function from SL/GL.pm transaction function - and replace the $form | element with a transaction object. | | Unfortunately there's absolutely NO comments in the code (great ;) so | there's a lot of things it does - that I'm not certain off (digging | through the $form element will probably help there). | | One of you talked about having recorded which SQL queries were done for | the different actions - I could use a list of SQL queries it runs, when | posting a new general ledger transaction - to doublecheck. | | I'd be happy to hear if any of you have any design ideas? or if you just | like my idea :) | | Also - if we could identify some tasks that we each would like to work | on (usually because we need to use them ourselves) - that way we can | create a list of tasks, and who they are assigned to? - ------------------------------------------------------- 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) iD8DBQFCJgpvPToLeX4GPGIRAsG0AKCzR9cB5g/I3XKmvO6d2mMJhjc1EgCgp3n/ 8pbhFCtgi/2LpbsLhBPLeX4= =1UOU -----END PGP SIGNATURE----- |
|
From: Klavs K. <kl...@vs...> - 2005-03-02 18:16:33
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys, I'm looking at SL code -and I think I'll build the API "transaction" function from SL/GL.pm transaction function - and replace the $form element with a transaction object. Unfortunately there's absolutely NO comments in the code (great ;) so there's a lot of things it does - that I'm not certain off (digging through the $form element will probably help there). One of you talked about having recorded which SQL queries were done for the different actions - I could use a list of SQL queries it runs, when posting a new general ledger transaction - to doublecheck. I'd be happy to hear if any of you have any design ideas? or if you just like my idea :) Also - if we could identify some tasks that we each would like to work on (usually because we need to use them ourselves) - that way we can create a list of tasks, and who they are assigned to? - -- 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) iD8DBQFCJgMLPToLeX4GPGIRAt8aAJ4plm1jepE7/Ej2zePb6+ZisikU5gCfeOo6 ZkuoXNhX2d5VLAwX5bOFa0I= =DTaZ -----END PGP SIGNATURE----- |
|
From: Klavs K. <kl...@vs...> - 2005-03-02 16:26:33
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 on 01-03-2005 22:43 Tony Fraser wrote: [SNIP] | What I'm thinking is that the API could sit on top of the GUI. In the | past we've talked about something that could be used to re-implement the | GUI but I really think that anything we do to that layer of SL would be | best started as a re-write/re-implementation of SL that is DB schema | compatible. | Which is exactly what we talked about - reimplementing the features the GUI (and other programs/scripts) need in the API - and then make the GUI use that instead of running SQL-ledger gui on the side, which will be what I'll do until a new GUI, using the API is ready. | In the meantime I think the immediate thing to do is to create an API | that interacts with SL through a combination of LWP::UserAgent and | HTML::Form. We could make the API SL specific or we could generalize the | API and make a backend for it that interacts with the current SL. | This is what I'm doing now - using lynx and posting what I need to do. One could use WWW::Mechanize to great benefit, but it is hard work, and because of the way the GUI works - you'll have to duplicate the data (like internal partnumbers etc.) unless, you use WWW::Mechanize (which acts as a browser). I hate this approach with my entire soul - which is why I wanted to start the openledger project :) I currently post invoices this way - and am going to write the first 2 functions for the API this/next week: 1) a function for registering a simple transaction (I need to move money around, when they've been charged from a credit card - I need to move them to my bank account - to reflect what happens in real life :) 2) I need a "getInvoice" function, which will fill an Invoice object (see CVS for how that object looks) - so I can give the API an invoicenumber, and get the invoice, including the ordernumber, which is what I need in this case. | I have some UML (created with Dia) of a possible generalized API. I | wouldn't mind getting some comments on the API. I'll post the UML on the | SF.net project webspace later today. | | So what do you people thing of interacting with SL through HTTP | requests? I think it will be the most straight forward and probably the | most SL-version-non-specific way I can come up with. | AFAIK the DB structure of SL has been more stable than the GUI design, and I have done what you are talking about - it is a very tiresome approach - and if Dieter gets tired of us - it wouldn't be hard to change the GUI a little bit -which would mean a lot of updating on our part. I use the same method (WWW::Mechanize) for updating modules in PostNuke. I definetely prefer the path, which leads to a community-based accounting system :) - -- 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) iD8DBQFCJelDPToLeX4GPGIRAsVSAKCSCf3/qmgRUFmzh5R9DQBY3ouVqwCeIWFI lSLUypk9djvZl5aIQHJpAX4= =WS6U -----END PGP SIGNATURE----- |
|
From: Tony F. <to...@sy...> - 2005-03-01 21:43:53
|
I have been thinking quite a bit about how to implement an API for 3rd party/custom apps to use SL. The solution I have come up with is not exactly what has been talked about on this list in the past, but I think it could work quite well. It won't help future SL development at all though. What I'm thinking is that the API could sit on top of the GUI. In the past we've talked about something that could be used to re-implement the GUI but I really think that anything we do to that layer of SL would be best started as a re-write/re-implementation of SL that is DB schema compatible. In the meantime I think the immediate thing to do is to create an API that interacts with SL through a combination of LWP::UserAgent and HTML::Form. We could make the API SL specific or we could generalize the API and make a backend for it that interacts with the current SL. I have some UML (created with Dia) of a possible generalized API. I wouldn't mind getting some comments on the API. I'll post the UML on the SF.net project webspace later today. So what do you people thing of interacting with SL through HTTP requests? I think it will be the most straight forward and probably the most SL-version-non-specific way I can come up with. -- Tony Fraser to...@sy... Sybaspace Internet Solutions System Administrator phone: (250) 246-5368 fax: (250) 246-5398 |
|
From: Klavs K. <kl...@vs...> - 2005-03-01 18:33:27
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 on 28-02-2005 18:33 Joseph wrote: | Is this project doing any progress? | I've not seen a single post since Feb.21/05 on this forum. | The last is from the 22/5 :) - and unfortunately no, it has been VERY quiet :( | How many members do we have? | 12. I'm going to start the API, by writing a function to post a transaction (not invoice etc.) - as I need it to automatically register when money (from credit card payments) are actually on my account - until they are, they are on a special account for "uncashed credit card payments". - -- 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) iD8DBQFCJLVrPToLeX4GPGIRAmcqAJ9ErmhRX5cgawBIxmZ0EFcby3fw0ACfZB+/ oX75UPIRgHkeGXvXRoKmD3A= =ViIJ -----END PGP SIGNATURE----- |
|
From: Joseph <sy...@in...> - 2005-02-28 17:33:09
|
Is this project doing any progress? I've not seen a single post since Feb.21/05 on this forum. How many members do we have? -- #Joseph |
|
From: Ang T. C. <tc...@st...> - 2005-02-21 16:28:48
|
Klavs Klavsen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > > on 21-02-2005 23:54 Ang Tun Chek wrote: > | Hi > | i have 2 question for the new Invoice Class > | How the modules knows if there is 2 items with same partnumber if you > | take out the part_id? > For this to work, the partnr (ie. NOT the internal part_id) will have to > be unique - but I can't think of any reason for it not to be. Ofcourse > before posting, we'll have to look up the part_id (in the API) and if > there's more than one match for the given partnr, ofcourse it'll have to > throw an error. i have a customer using OBA where partnumber not unique is required. they required a same partnumber but similar description with extra wording. > I'll welcome all suggestions :) > IMHO we need to avoid the client having to need so many unnecessary > things (as said before, such as internal partnumbers, expenseaccno pr. > part etc.). > > | is there any GUI ready to link to invoice class? > | > No. I don't think anyone wants to start work on a GUI, until we have a > fully functional API. As we use the exact same db-structure (for now > atleast) you can use SQL-Ledger as a webfrontend. > > [SNIP] > - -- > 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) > > iD8DBQFCGfgSPToLeX4GPGIRAimoAKCbwgAQYZ9ePw9LWAf4ty1tPHqRgwCggcgc > 9v02/WnFApaHlpWe3Drv9po= > =0JkH > -----END PGP SIGNATURE----- > > > ------------------------------------------------------- > 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 > |
|
From: Klavs K. <kl...@vs...> - 2005-02-21 16:27:08
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Ang, You forgot to choose "Reply to all" again ;) on 22-02-2005 01:25 Ang Tun Chek wrote: | Klavs Klavsen wrote: [SNIP] |> i have a customer using OBA where partnumber not unique is |> required. they required a same partnumber but similar description |> with extra | wording. You can change the item text (in the invoice object you simply put what text you want - and it is saved with the invoice) - without having to have a new itemnr. I do that. If it's the same item - it should have the same itemnr. - not good to have different itemnumbers for same item - as stock won't fit anymore either. [SNIP] - -- 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) iD8DBQFCGgvcPToLeX4GPGIRAkEpAJ9WDv8/NNylVECB5nTeSsTb2muf8QCfbJMu hKu9RzmMtIv1EpuKtGfJVOU= =gft8 -----END PGP SIGNATURE----- |
|
From: Klavs K. <kl...@vs...> - 2005-02-21 15:02:41
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 on 21-02-2005 23:54 Ang Tun Chek wrote: | Hi | i have 2 question for the new Invoice Class | How the modules knows if there is 2 items with same partnumber if you | take out the part_id? For this to work, the partnr (ie. NOT the internal part_id) will have to be unique - but I can't think of any reason for it not to be. Ofcourse before posting, we'll have to look up the part_id (in the API) and if there's more than one match for the given partnr, ofcourse it'll have to throw an error. I'll welcome all suggestions :) IMHO we need to avoid the client having to need so many unnecessary things (as said before, such as internal partnumbers, expenseaccno pr. part etc.). | is there any GUI ready to link to invoice class? | No. I don't think anyone wants to start work on a GUI, until we have a fully functional API. As we use the exact same db-structure (for now atleast) you can use SQL-Ledger as a webfrontend. [SNIP] - -- 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) iD8DBQFCGfgSPToLeX4GPGIRAimoAKCbwgAQYZ9ePw9LWAf4ty1tPHqRgwCggcgc 9v02/WnFApaHlpWe3Drv9po= =0JkH -----END PGP SIGNATURE----- |
|
From: Ang T. C. <tc...@st...> - 2005-02-21 14:47:38
|
hi everyone,
i hope my function can help
sub last_invoice {
my ($self, $myconfig, $form) = @_;
# connect to database
my $dbh = $form->dbconnect($myconfig);
# get the last invnumber
my $query = qq|select lastinvnumber from (SELECT id,invnumber as
lastinvnumber
FROM ar
WHERE invoice='t' and transtype='$form->{transtype}' order
by id desc limit 2) as foo order by id DESC|;
my $sth = $dbh->prepare($query);
$sth->execute || $form->dberror($query);
$ref = $sth->fetchrow_hashref(NAME_lc);
map { $form->{$_} = $ref->{$_} } keys %$ref;
$sth->finish;
$dbh->disconnect;
}
This code is derived from "Open Business Accounting (OBA)". OBA uses a
variable "transtype" to control different type of "Invoices/AR". Ex, use
can create Cash Sales , Invoice , Consignment Notes or etc using the
same module with its own running number.
from
Ang Tun Chek
Klavs Klavsen wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi guys,
>
> Currently SL's way of handling invoicenumbers does NOT work for me. It
> does not increment as it should and I have no way of defining a specific
> pattern I'd like (f.ex. $year-incnr, $year$xdigitincnr or
> $year$month$day$hour$min$sec etc. ).
>
> I was thinking that I'd add a function that gives you the next available
> invoicenumber (ie. whatever invoicenumbering scheme you use - +1 :) and
> also I'd like to make PostInvoice able to handle this, if the invoicenr.
> field is left out, it should automatically assign it the next available
> invoicenr.
>
> My reasoning for doing this, is that I currently handle invoicenumbers
> in my own scripts - and IMHO this is (again :) the responsibility of the
> accounting system - my scripts should not have to care about that for
> posting a mere invoice.
>
> I think I'll build the "get next invoicenr." function to use a
> openledger.conf file in which you can define the pattern - to begin with
> I'll build it to support the sceme I use, which is the $year followed by
> a 5 digitnr. in my case (ie. any invoicenumber is padded with zero's to
> always be 5 digits). I'll let the digit amount be defineable ofcourse -
> probably the printf way.
>
> What do you think? Any ideas to implementing it will be welcome -
> otherwise I'll just think of a way to get it rolling when I get to it :)
>
> I was thinking of a $InvoiceNumber variable to be defined in
> openledger.conf which would simply be used in printf - and any variables
> given in it, should also (somehow) be chosen from a predefined set in,
> and defined in openledger.conf.
>
> - --
> 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)
>
> iD8DBQFCGZcoPToLeX4GPGIRArfTAJ9Ip5/aRglIdo1g/MpFSU+10kFDjgCfXpy1
> KZgsUz6HubzHQ4tvKMuave4=
> =EoGG
> -----END PGP SIGNATURE-----
>
>
> -------------------------------------------------------
> 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
|
|
From: Ang T. C. <tc...@st...> - 2005-02-21 14:45:20
|
Hi i have 2 question for the new Invoice Class How the modules knows if there is 2 items with same partnumber if you take out the part_id? is there any GUI ready to link to invoice class? Klavs Klavsen wrote: > -----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----- > > > ------------------------------------------------------- > 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 |
|
From: Klavs K. <kl...@vs...> - 2005-02-21 08:09:09
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys, Currently SL's way of handling invoicenumbers does NOT work for me. It does not increment as it should and I have no way of defining a specific pattern I'd like (f.ex. $year-incnr, $year$xdigitincnr or $year$month$day$hour$min$sec etc. ). I was thinking that I'd add a function that gives you the next available invoicenumber (ie. whatever invoicenumbering scheme you use - +1 :) and also I'd like to make PostInvoice able to handle this, if the invoicenr. field is left out, it should automatically assign it the next available invoicenr. My reasoning for doing this, is that I currently handle invoicenumbers in my own scripts - and IMHO this is (again :) the responsibility of the accounting system - my scripts should not have to care about that for posting a mere invoice. I think I'll build the "get next invoicenr." function to use a openledger.conf file in which you can define the pattern - to begin with I'll build it to support the sceme I use, which is the $year followed by a 5 digitnr. in my case (ie. any invoicenumber is padded with zero's to always be 5 digits). I'll let the digit amount be defineable ofcourse - probably the printf way. What do you think? Any ideas to implementing it will be welcome - otherwise I'll just think of a way to get it rolling when I get to it :) I was thinking of a $InvoiceNumber variable to be defined in openledger.conf which would simply be used in printf - and any variables given in it, should also (somehow) be chosen from a predefined set in, and defined in openledger.conf. - -- 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) iD8DBQFCGZcoPToLeX4GPGIRArfTAJ9Ip5/aRglIdo1g/MpFSU+10kFDjgCfXpy1 KZgsUz6HubzHQ4tvKMuave4= =EoGG -----END PGP SIGNATURE----- |
|
From: Klavs K. <kl...@vs...> - 2005-02-21 07:51:18
|
-----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----- |
|
From: Udo S. <udo...@gm...> - 2005-02-15 16:37:34
|
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 |
|
From: atchek <at...@ew...> - 2005-02-11 16:51:12
|
To All,
i had been working on OBA to produce a business software which is best towards small to medium
organisation and more concern on accounting and inventory section. i listed all the features in OBA
compare to SL for your reference. So i hope we can combine the everything together which can adapt
SL and OBA.
New Modules
===========
* Membership support
* Quick Entry
- Alternative to Add General Ledger for quicker data entry
* Invoice/Order Listing
- A report to show who buy/sell what.
* Stock Value Report
- A summary report to re-sum all balance in,out,adjust and compare with the
figure saved in the inventory in ic table in the database
* Sales/Purchase Summary for customer
- shows how much customer/vendor buy/sell from you
* Sales/Purchase Summary for inventory
- shows how much item had been bought/sold
* Debit/Credit note
* stock adjustment
- A new module to record any adjustment has to made to the balance quantity
of an item
* yearly aging
* GL summary
- A report to summary all GL transaction which group by transaction type or project
Enhancement
===========
* Order Entry
* A new standard template is created which can be modified to become all sort of order
entry such as Purchase Order, Sales Order , Quotation, Purchase Requiesition, RFQ
through the modification on the menu.ini
* new field
* added status - open, closed and KIV
* added transcation type - to differentiate all orders
* Invoice
* Cash Sales - able to add payment automatically
* new field
* sales person
* membership
* Added transaction type for accounting purpose
* sub no - sub contractor
* projects
* OBA now support tax on total and tax on item
* new invoice printing
* print title and heading on all pages
* balance bring forward on next page
* IO.pl
* new field
* Order Number - used for calculate order balance for large order quantity
* Tax - Tax on item
* General Ledger
* Added transaction type for accounting purpose
* sub no - sub contractor
* projects
* Inventory
* Added Combo as new Inventory type - best for manufacturing to group similar items
* History report - able to figure opening balance with the given 'from' date
* Quantity Balance - shows quantity balance and purchase cost
* chart of account
* added new account type - debtor, creditor ,cogs, profit and loss, appropriation, fixed asset
* customer/vendor
* treat all customer/vendor as debtor/creditor accordingly
* new COA will be added if new customer/vendor is added
* new field
* group - code to group customer/vendor which also allow invoice to show specific
group of customer/vendor through menu.ini
* location code
* Receipt/Payment
* able to save as a record
* comes with it own running receipt/payment number
* Trial Balance
* 3 types of Trial Balance added
* balance sheet
* able to show fixed asset and depreciation properly
Others
======
* OBA comes with simple and advance searching for beginner and expert user
* enhance on report engine
* new report printing support
* print title and heading on all pages
* balance bring forward on next page
* sub heading displayed if subtotal is ticked
* users now can modify menu.ini to customise the report without touching the
actual coding
For more information, please refer to http://oba.sourceforge.net and visit the demo
--
Open WebMail Project (http://openwebmail.org)
Debian Project (http://www.debian.org)
|
|
From: Ang T. C. <at...@ew...> - 2005-02-07 16:50:29
|
To all, i am off for chinese new year holiday for few days. i will be back with some works cheers Ang Tun Chek |
|
From: Klavs K. <kl...@vs...> - 2005-02-06 17:18:31
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well this construct is IMHO what we already have. the XML part, is in CVS called SOAP-API (seperate module/top-folder) and it needs to be split out, in what belongs in the openledger-api and what belongs in the SOAP-api - and then the openledger-api needs to have added new functions (IMHO to start with, simply copying code/restructuring from SL will be fine). Once we have something that's working well enough for everyone, several projects can begin: 1) build a GUI, to use the new API, instead of implementing it's own db-access. This GUI should IMHO be template-based, but I'll leave the design up to those, who wants to write it. Ofcourse, we as a community/team can decide if we want to accept the code - but some code is (in most cases - openledger MUST be stable - no accidents with peoples accounting-data! ;) better than no code :) 2) expand the SOAP-API to support all the functions the openledger-api has, so everyone can use the accounting capabilities of openledger, over a network (or locally) - no matter what language they use. 3) construct an object-oriented openledger-api - this might be done in part or in whole, in the first openledger-api - depending on who codes it, and their preferences. The most important part, is that we get somthing working as fast as possible - to attract devs and users. ... Anything we can think off, and more :) on 06-02-2005 17:51 Ang Tun Chek wrote: | +----------+ +---+ +------------+ | | JAVA | <-> | | <-> | | | +----------+ | | | | | | | | | | +----------+ | | | | | | PYTHON | <-> | X | | OPENLEDGER | | +----------+ | | | | | | M | | API | | +----------+ | | | | | | C/C++ | <-> | L | | | | +----------+ | | | | | | | <-> | | | +----------+ | | | | | | OTHER | <-> | | | | | +----------+ +---+ | | | | | | +---------------------+ | | | | PERL FRONTEND | <-> | | | +---------------------+ +------------+ | | | | | - -- 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) iD8DBQFCBlGEPToLeX4GPGIRAgX7AJ0TOeFFG6NKLMf8xxIFOGVX2W+e9ACfRNQl YfCTc7jufJRd72fOYcQQrEI= =wj2H -----END PGP SIGNATURE----- |
|
From: Ang T. C. <at...@ew...> - 2005-02-06 16:50:59
|
+----------+ +---+ +------------+
| JAVA | <-> | | <-> | |
+----------+ | | | |
| | | |
+----------+ | | | |
| PYTHON | <-> | X | | OPENLEDGER |
+----------+ | | | |
| M | | API |
+----------+ | | | |
| C/C++ | <-> | L | | |
+----------+ | | | |
| | <-> | |
+----------+ | | | |
| OTHER | <-> | | | |
+----------+ +---+ | |
| |
+---------------------+ | |
| PERL FRONTEND | <-> | |
+---------------------+ +------------+
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.5 - Release Date: 2/3/2005
|
|
From: Ang T. C. <at...@ew...> - 2005-02-06 16:50:01
|
+----------+ +---+ +------------+
| JAVA | <-> | | <-> | |
+----------+ | | | |
| | | |
+----------+ | | | |
| PYTHON | <-> | X | | OPENLEDGER |
+----------+ | | | |
| M | | API |
+----------+ | | | |
| C/C++ | <-> | L | | |
+----------+ | | | |
| | <-> | |
+----------+ | | | |
| OTHER | <-> | | | |
+----------+ +---+ | |
| |
+---------------------+ | |
| PERL FRONTEND | <-> | |
+---------------------+ +------------+
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.8.5 - Release Date: 2/3/2005
|
|
From: Klavs K. <kl...@vs...> - 2005-02-01 16:00:40
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi guys, Welcome to the new list. Unfortunately it does NOT seem as if SF will move the old archive of emails to the new list :( I might just resend them all.. - -- 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) iD8DBQFB/6e9PToLeX4GPGIRAvFAAJ0b4G6usp15GWpYMmCHeMnng2SWVwCeKDoS pVhBk83B0cknDA9siktCDkQ= =8c9L -----END PGP SIGNATURE----- |
