Just as an update, I have uploaded PGObject and PGObject::Simple to CPAN.
These together are a nearly complete and generalized eqivalent to
DBObject. What is currently missing is the type registration framework we
will need for dates and numeric types. The code is refactored and the
interfaces c
Can you be more specific?
The general Perl object you probably want to use is
LedgerSMB::DBObject::Menu and since this inherits from LedgerSMB::DBObject,
the simplest way to do this is to create a user defined function in
PostgreSQL. From there it is very straight-forward to pull that data into
L
Chris writes:
> However such an approach restricts you to accurate accounting
> information on a monthly basis.
It works the same way if you post the tranfers daily. Then it's just
$.21918/day instead of $6.67/month.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
On Mon, May 27, 2013 at 8:32 AM, John Hasler wrote:
> Chris writes:
> > So if I pay $80 for a year of hosting on October 1, you would
> > materialize $20 in income on that year, and $60 the next year. Most of
> > the time this is not really material but there are cases when it could
> > be, since
>>(and patch the rest of the app
to direct here).
I'm not sure how to. If I can get some direction on how to pull
from the database, I'm set.
Thanks.
Brian
B
Thank you for your previous feedback. I want to extend the menu by
inserting some additional links WITHOUT adding entries in the
menu_node, menu_acl and menu_attribute tables. It looks like it can
be done from scripts/menu.pl; since Perl is not my best language,
I'm str
Chris writes:
> So if I pay $80 for a year of hosting on October 1, you would
> materialize $20 in income on that year, and $60 the next year. Most of
> the time this is not really material but there are cases when it could
> be, since recognizing all income at the beginning of the contract can
> i
Brian writes:
> The real issue is: if the shipment is lost or damaged, who is
> responsible?
Whoever owns the goods at the time the damage occurs.
In practice I've always found that it works well to arrange for the act
of shipment to trigger invoicing.
--
John Hasler
jhas...@newsguy.com
Elmwo
On Mon, May 27, 2013 at 6:16 AM, Brian Wolf wrote:
> Both Chris and Erik have made good points regarding the accounting
> aspect of this issue.
>
> Can someone clarify:
> Does the product transfer ownership to the customer when it is shipped, or
> when received?
>
This depends on who accepts ris
On Mon, May 27, 2013 at 6:33 AM, Brian Wolf wrote:
> The real issue is: if the shipment is lost or damaged, who is
> responsible?
>
Bingo.
> In other words, does shipping itself determine income? Or, is it a
> separate step?
>
It may. On the other hand if I ship you something with an option
The real issue is: if the shipment is
lost or damaged, who is responsible?
In other words, does shipping itself determine income? Or, is it
a separate step?
Thanks.
Brian
Brian Wolf writes:
> Does the product transfer ownership to the customer when it is shipped, or
> when received?
Depends on who pays for the shipping. If the customer pays the shipper
is his agent and receives it on his behalf when you ship. If you pay
the shipper is your agent and the customer
Both Chris and Erik have made good
points regarding the accounting aspect of this issue.
Can someone clarify:
Does the product transfer ownership to the customer when it is
shipped, or when received? Those points in time may be days
apart. Is inco
Hi Chris,
>> Reading the wikipedia page on invoices confirms my understanding of the
position of the invoice document. If you want to receive money in advance,
a proforma invoice can be used, or an order can state pre-payment is
required before shipment will take place.
>>
>> If LSMB could automat
Hi everyone,
LedgerSMB 1.3.33-rc2 is available for testing. Compared to rc1 this
includes a fix to the on hold toggle fix, and a fix to addresses
dissapearing from the invoice user interface on update (this is the new
address indicator added in 1.3.32).
Please feel free to download and test. I
15 matches
Mail list logo