sql-ledger-users — SQL-Ledger users

[SL] Hot Keys on Firefox 2

[Penguin P. <pen...@gm...>]

Hi

I recently upgraded to Firefox 2.0 and have found that the Hot Keys ie.
Alt-I, Alt-u or Alt-s etc now dont work  on Sql-Ledger. If I put the Cursor
over the relevant button it still shows the Hot Key Alternative but it is
not active. Is there something I need to activate on firefox to allow me to
use the hot keys? I realise I most probably am missing something obvious but
cant seem to see it.

Many Thanks
Tim

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi 

The power user got back to me.

The Sever time was 12:53 and the Windows Client time was 13:11.

Can someone also explain if this is the possible causes
I will restart the ntp when I pop over there today.

Cheers

On Wed, 2006-11-15 at 12:53 +0000, Richard Patterson wrote:
> Chuck Amadi Systems Administrator wrote:
> > Hi List 
> >
> > SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> > to keep inputting our password all the time.
> >
> > Cheers List
> >
> >
> >   
> If you have not changed your session time-outs then check that the time
> on the server matches the time on your clients...
> 
> Regards
> 
-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi Unfortunamtly for me

The Linux finance Server is based at a remote office.

So I have spoken to a power user to admin the server and type the date
command
if the user is able to get a xterm prompt and to check her Windows
Client date/time clock if not I got a trip this afternoon.

I will thus restart the ntp daemon on the finance server.
So if there is any other checks I ca do please let me know So 
I am armed and dangerous when I pop out later.

Thanks

On Wed, 2006-11-15 at 12:53 +0000, Richard Patterson wrote:
> Chuck Amadi Systems Administrator wrote:
> > Hi List 
> >
> > SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> > to keep inputting our password all the time.
> >
> > Cheers List
> >
> >
> >   
> If you have not changed your session time-outs then check that the time
> on the server matches the time on your clients...
> 
> Regards
> 
-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi List Sorry but I forgot to mention their using IE6
SL is installed on a Linux SLES 9 Server But the user access
SL and Postgresql via IE Browser web interface.

SQL Version 2.6.19 has been acting up since the last upgrade.  We have
to keep inputting our password all the time.

PS Thus I gather it's a possible cache issue Please email suggestions or
good links

Cheers List


On Wed, 2006-11-15 at 12:21 +0000, Chuck Amadi Systems Administrator
wrote:
> Hi List 
> 
> SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> to keep inputting our password all the time.
> 
> Cheers List
> 
> 
-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi Paul

Thanks for your tip

But the Session Timeout is set as default which is 3600 seconds (1hour).
Unfortunately for me as SysAdmin there session expires well before 3600
seconds.

I have gooogled around (looking at my docs)but no joy So I will continue
my search for a remedy
before utilising my paid up support with Dieter.

Cheers

On Wed, 2006-11-15 at 13:39 +0100, Paul Tammes wrote:
> Chuck Amadi Systems Administrator schreef:
> > Hi List 
> >
> > SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> > to keep inputting our password all the time.
> >
> > Cheers List
> >
> >
> >   
> use admin.pl to set user defaults for time-out to higher standards might 
> be a solution?
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
> 
-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Richard P. <ri...@he...>]

Chuck Amadi Systems Administrator wrote:
> Hi List 
>
> SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> to keep inputting our password all the time.
>
> Cheers List
>
>
>   
If you have not changed your session time-outs then check that the time
on the server matches the time on your clients...

Regards

-- 

Richard Patterson          HelpQuick Limited
Tel: 0191 2582888          Fax: 0191 6408666
Jabber chat:  ri...@ja...
Web:     http://www.helpquick.co.uk

Re: [SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Paul T. <pt...@wa...>]

Chuck Amadi Systems Administrator schreef:
> Hi List 
>
> SQL Version 2.6.19 has been acting up since the last upgrade.  We have
> to keep inputting our password all the time.
>
> Cheers List
>
>
>   
use admin.pl to set user defaults for time-out to higher standards might 
be a solution?

[SL] SQL Version 2.6.19 has been acting up since the last upgrade. We have to keep inputting our password all the time.

[Chuck A. S. A. <ch...@sm...>]

Hi List 

SQL Version 2.6.19 has been acting up since the last upgrade.  We have
to keep inputting our password all the time.

Cheers List


-- 
Unix/ Linux Systems Administrator
Chuck Amadi
The Surgical Material Testing Laboratory (SMTL), 
Princess of Wales Hospital 
Coity Road 
Bridgend, 
United Kingdom, CF31 1RQ.
Email chuck.smtl.co.uk
Tel: +44 1656 752820 
Fax: +44 1656 752830

Re: [SL] Programatically Entering Sales Orders

[R P. <arc...@mt...>]

On Monday 13 November 2006 2:34 pm, Tony Fraser wrote:
> On Mon, 2006-11-13 at 14:32 -0500, C. Duncan Hudson wrote:
> > I have several shell scripts that load invoices & pos, and which
> > print 
> > pick lists.  I'm in the process of moving them all to
> > LWP::UserAgent.  
> > The way I see it I'm safer with LWP then I am with the API - the API 
> > requirements are far more likely to change then the screens are.
> > Even 
> > if the screens do change then it's pretty straight forward updating
> > the 
> > Perl script.  Also, I agree that it's better to not have to shell to 
> > call the API as that's just another point of failure.  It's also 
> > difficult to determine whether the API call actually worked or not.
> > I 
> > think there was some talk, along time ago, about a Perl module for 
> > SQL-Ledger, but that would get outdated in no time.  LWP, in my
> > opinion, 
> > is a better fit.
> 
> I agree with your LWP opinion. The API and the HTML forms are basically
> the same. All the API is is a way to supply the CGI scripts a query
> string as a command line parameter. I also think that scripts that use
> LWP (or any HTTP library) are more flexible, all they need is HTTP
> access to you SQL Ledger installation. They don't need to run locally on
> the SQL Ledger server.
> 
> Some time ago I wrote this proof of concept code:
> http://openledger.sourceforge.net/SL-Api.tar.gz
> 
> Basically, it provides a simple to understand PERL API by automating the
> SQL Ledger web interface with LWP anf HTML::Form in the background. As
> it was only a proposal and no one showed any interest in it at the time
> it only works with the GL. Adding more modules shouldn't be a big deal
> though.

When I had to repost a bunch of invoices to solve a COGS out of order problem, I used 
WWW:Mechanize which wraps up functionality found in LWP.   Works with HTTPS too.
Nice and simple..... goto page... fill form..submit form.......  :)

http://cpanratings.perl.org/dist/WWW-Mechanize
http://search.cpan.org/~petdance/WWW-Mechanize/

Cheers !
Roy

Re: [SL] Example of booking depreciable assets and depreciation?

[David J <ja...@in...>]

Ed
Talk to your accountant, or google for Accounting 101.
Why the double shuffle with the acquisition ?
And to depreciate :
Dr Depreciation expense
Cr Accumulated Depreciation.
Don't touch the cost.
You're welcome
David J 

> Hi
> 
> I'm sure that there are plenty of examples somewhere on
> the SL list, but  I couldn't locate any easily with
> google.
> 
> Can someone please give me an example of the transactions
> required to  book buying an item like an office printer,
> then adding it to the  depreciable assets and finally
> knocking off 40% for the first years  depreciation?
> 
> - I am using a fairly close to default COA. 
> - I buy my printer with an AP invoice, booking it into
> something  like an admin expenses account called "Computer
> Expenses".  - I then put in a journal entry to transfer it
> from here into my capital  assets ledger: "Office
> Furniture & Equipment " - Then I put in another
> transaction to shift 40% from the capital assets  account
> into "Accum. Amort. -Furn. & Equip. "
> 
> This all looks nearly correct on the balance sheet, but I
> don't appear  to have the depreciation turning up on the
> Income Statement report?   What am I missing?  Does this
> sound like the correct way to book the  transaction?
> 
> 
> What I *think* I am doing wrong is that last transaction? 
> Should the book assets account remain showing the full
> book value of the assets, and instead the transaction is
> something like credit "Computer expenses", debit "Accum.
> Amort. -Furn. & Equip. "?  This would seem to make more
> sense
> 
> Also, would it be better to set up the COA so that the AP
> invoice directly books into the capital assets account?  I
> guess Dieter intended these kinds of capital assets to be
> entered directly using a GL transaction rather than an AP
> invoice? In my case it's useful to track the seller
> details though
> 
> So, in conclusion should the correct transactions be:
> 
> - AP invoice -> Office Furniture and Equip (asset account)
> - GL: "Accum. Amort. -Furn. & Equip. " -> "Computer
> Expenses" (or similar cost account?)
> 
> Cheers
> 
> Ed W
> 
>

Re: [SL] Programatically Entering Sales Orders

[Tony F. <to...@sy...>]

On Mon, 2006-11-13 at 14:32 -0500, C. Duncan Hudson wrote:
> I have several shell scripts that load invoices & pos, and which
> print 
> pick lists.  I'm in the process of moving them all to
> LWP::UserAgent.  
> The way I see it I'm safer with LWP then I am with the API - the API 
> requirements are far more likely to change then the screens are.
> Even 
> if the screens do change then it's pretty straight forward updating
> the 
> Perl script.  Also, I agree that it's better to not have to shell to 
> call the API as that's just another point of failure.  It's also 
> difficult to determine whether the API call actually worked or not.
> I 
> think there was some talk, along time ago, about a Perl module for 
> SQL-Ledger, but that would get outdated in no time.  LWP, in my
> opinion, 
> is a better fit.

I agree with your LWP opinion. The API and the HTML forms are basically
the same. All the API is is a way to supply the CGI scripts a query
string as a command line parameter. I also think that scripts that use
LWP (or any HTTP library) are more flexible, all they need is HTTP
access to you SQL Ledger installation. They don't need to run locally on
the SQL Ledger server.

Some time ago I wrote this proof of concept code:
http://openledger.sourceforge.net/SL-Api.tar.gz

Basically, it provides a simple to understand PERL API by automating the
SQL Ledger web interface with LWP anf HTML::Form in the background. As
it was only a proposal and no one showed any interest in it at the time
it only works with the GL. Adding more modules shouldn't be a big deal
though.

-- 
Tony Fraser
to...@sy...
Sybaspace Internet Solutions                        System Administrator
phone: (250) 246-5368                                fax: (250) 246-5398

Re: [SL] Programatically Entering Sales Orders

[C. D. H. <Du...@Du...>]

Ted Onley wrote:
> I've written some scripts to import customer orders and purchase orders, but 
> they use the API.  If you don't use the API, then you are bypassing all the 
> business rules built into SQL-Ledger.  There are also many validation checks 
> done in the API to maintain data integrity.  It may be a little more work 
> shelling out and running a script to use the API, but the amount of work you may 
>   face fixing data integrity issue may far out weigh the work required on an API 
> call.
>   
I have several shell scripts that load invoices & pos, and which print 
pick lists.  I'm in the process of moving them all to LWP::UserAgent.  
The way I see it I'm safer with LWP then I am with the API - the API 
requirements are far more likely to change then the screens are.  Even 
if the screens do change then it's pretty straight forward updating the 
Perl script.  Also, I agree that it's better to not have to shell to 
call the API as that's just another point of failure.  It's also 
difficult to determine whether the API call actually worked or not.   I 
think there was some talk, along time ago, about a Perl module for 
SQL-Ledger, but that would get outdated in no time.  LWP, in my opinion, 
is a better fit.

Dunc

Re: [SL] Programatically Entering Sales Orders

[Mark B. <ma...@ga...>]

On Mon, Nov 13, 2006 at 10:31:48AM -0800, Dave Snell wrote:

> I take it you're not a Perl developer.  
 
Indeed, the only reason I use Perl is b/c of Sql Ledger.

> LWP is a "set of Perl modules which provides a simple and
> consistent application programming interface (API) to the
> World-Wide-Web".  

I never heard of it--it sounds useful, thanks for the tip.

m

Re: [SL] Programatically Entering Sales Orders

[Dave S. <bou...@ya...>]

--- Mark Bucciarelli <ma...@ga...> wrote:

> On Sun, Nov 12, 2006 at 08:13:13PM -0800, Dave Snell
> wrote:
> 
> By hitting the db directly, you will end up
> duplicating some
> subset of the application logic; for example, is
> customer ID
> valid, is part number valid, is part number active,
> etc, etc.
> 
> As app logic and/or table structure changes, you may
> need to
> update your script.  This could be painful and will
> be
> error-prone.
> 
> If (by some small chance) you insert data that
> doesn't satisfy
> the app's assumptions re: data integrity, who knows
> what kind of
> wierd bugs you could create.
> 
> Makes it much harder for Dieter to give you good
> support as well.
> If I was him I wouldn't support this at all.
> 
> Yeah, not using the API will make your scripts
> marginally faster
> but it doesn't seem worth it.

I take it you're not a Perl developer.  By using LWP I
wouldn't be skipping any of the application's edits, I
wouldn't be violating any referential integrity rules,
and I shouldn't end up with duplicate anything - as I
wouldn't be hitting the database directly.  LWP is a
"set of Perl modules which provides a simple and
consistent application programming interface (API) to
the World-Wide-Web".  In otherwords, I'd still be
using the application, it would just be a Perl program
that was stepping through the screens.  Not me, or one
of my staff.

B



 
____________________________________________________________________________________
Yahoo! Music Unlimited
Access over 1 million songs.
http://music.yahoo.com/unlimited

Re: [SL] Programatically Entering Sales Orders

[Ted O. <te...@on...>]

I've written some scripts to import customer orders and purchase orders, but 
they use the API.  If you don't use the API, then you are bypassing all the 
business rules built into SQL-Ledger.  There are also many validation checks 
done in the API to maintain data integrity.  It may be a little more work 
shelling out and running a script to use the API, but the amount of work you may 
  face fixing data integrity issue may far out weigh the work required on an API 
call.

Dave Snell wrote:
> Has anyone sucessfully used LWP to enter sales orders
> (or similar) into SQL-Ledger?  I have a perl
> application that  uses DBI to access several
> databases, and then eventually needs to update
> SQL-Ledger.  It just seems silly to shell out and call
> the API from the OS, when theoretically I could do it
> all from within the same perl script.
> 
> B
> 
> 
>  
> ____________________________________________________________________________________
> Yahoo! Music Unlimited
> Access over 1 million songs.
> http://music.yahoo.com/unlimited
> 
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> sql-ledger-users mailing list
> sql...@li...
> https://lists.sourceforge.net/lists/listinfo/sql-ledger-users
> 

Re: [SL] Programatically Entering Sales Orders

[Mark B. <ma...@ga...>]

On Sun, Nov 12, 2006 at 08:13:13PM -0800, Dave Snell wrote:

> It just seems silly to shell out and call the API from the OS,
> when theoretically I could do it all from within the same perl
> script.

By hitting the db directly, you will end up duplicating some
subset of the application logic; for example, is customer ID
valid, is part number valid, is part number active, etc, etc.

As app logic and/or table structure changes, you may need to
update your script.  This could be painful and will be
error-prone.

If (by some small chance) you insert data that doesn't satisfy
the app's assumptions re: data integrity, who knows what kind of
wierd bugs you could create.

Makes it much harder for Dieter to give you good support as well.
If I was him I wouldn't support this at all.

Yeah, not using the API will make your scripts marginally faster
but it doesn't seem worth it.

m

[SL] Programatically Entering Sales Orders

[Dave S. <bou...@ya...>]

Has anyone sucessfully used LWP to enter sales orders
(or similar) into SQL-Ledger?  I have a perl
application that  uses DBI to access several
databases, and then eventually needs to update
SQL-Ledger.  It just seems silly to shell out and call
the API from the OS, when theoretically I could do it
all from within the same perl script.

B


 
____________________________________________________________________________________
Yahoo! Music Unlimited
Access over 1 million songs.
http://music.yahoo.com/unlimited

[SL] Example of booking depreciable assets and depreciation?

[Ed W <li...@wi...>]

Hi

I'm sure that there are plenty of examples somewhere on the SL list, but 
I couldn't locate any easily with google.

Can someone please give me an example of the transactions required to 
book buying an item like an office printer, then adding it to the 
depreciable assets and finally knocking off 40% for the first years 
depreciation?

- I am using a fairly close to default COA. 
- I buy my printer with an AP invoice, booking it into something 
like an admin expenses account called "Computer Expenses". 
- I then put in a journal entry to transfer it from here into my capital 
assets ledger: "Office Furniture & Equipment "
- Then I put in another transaction to shift 40% from the capital assets 
account into "Accum. Amort. -Furn. & Equip. "

This all looks nearly correct on the balance sheet, but I don't appear 
to have the depreciation turning up on the Income Statement report?  
What am I missing?  Does this sound like the correct way to book the 
transaction?


What I *think* I am doing wrong is that last transaction?  Should the book assets account remain showing the full book value of the assets, and instead the transaction is something like credit "Computer expenses", debit "Accum. Amort. -Furn. & Equip. "?  This would seem to make more sense

Also, would it be better to set up the COA so that the AP invoice directly books into the capital assets account?  I guess Dieter intended these kinds of capital assets to be entered directly using a GL transaction rather than an AP invoice? In my case it's useful to track the seller details though

So, in conclusion should the correct transactions be:

- AP invoice -> Office Furniture and Equip (asset account)
- GL: "Accum. Amort. -Furn. & Equip. " -> "Computer Expenses" (or similar cost account?)

Cheers

Ed W

Re: [SL] Logon to NEW version??

[John W. F. <joh...@ve...>]

On Saturday 11 November 2006 02:32 pm, Brian Goodyear wrote:
> HI.  I currently have version 2.6.3 running fine.  I upgraded using the
> debian package (because setup.pl can't seem to get the new version) and
> would now like to logon to the new version.
>
> I suspect it's very obvious but I can't find out how from doing an archive
> search.
> Thanks in advance.
-----------------------------------------------------------------------------------
I had problems  (several) with the Debian package in Stable. I run a 
production system so I can not play with Etch. I got some help here that 
applied to both the Debian installation and to the install using setup.pl 
from the internet. It had to do with an error re: createlang for postgresql. 
However you do not mention that. I finally gave up on debian because it 
appears that the maintainer stripped out all of the example charts of 
accounts and much of the other stuff. I may be way off on that but none were 
installed on my system when I tried using the .deb package. The up shot is 
that I went to the installation from the internet & using setup.pl (after 
changing some permissions) it worked flawlessly & I have a full production 
system running great. FYI: I had not tried SQL-Ledger in several years so it 
was a great surprise to see how much it has improved.
-- 
John W. Foster

[SL] Logon to NEW version??

[Brian G. <br...@go...>]

HI.  I currently have version 2.6.3 running fine.  I upgraded using the
debian package (because setup.pl can't seem to get the new version) and
would now like to logon to the new version.

I suspect it's very obvious but I can't find out how from doing an archive
search.
Thanks in advance.

-- 
brian

Re: [SL] Indirect income and inventory managent

[Jeff V. <jv...@ch...>]

On Fri, 2006-11-10 at 13:39 +0200, Aschwin van der Woude wrote:
> Hi,
> 
> Here at work I am taking care of a fancy coffee-machine that uses a
> cash-card system for payments, and I decided to use sql-ledger to keep
> track of inventory and transactions. The idea is not to make profit on
> coffee-sales, but to charge people only the costs involved.
> 
> But I have a problem accounting properly for my used inventory.
> 
> The sales process is as follows:
>     * Cash cards are refilled once in a while and I receive money 
>       for this. These transaction are nicely recorded in sql-ledger.
>     * People use their cash cards to pay for coffee-drinks and the 
>       machine keeps track of how many times each coffee option is 
>       used. These transaction aren't recorded in sql-ledger even 
>       though inventory is used, but no money is received.
> 
> The inventory process is as follows
>     * Inventory is received from vendors and payments are recorded in 
>       sql-ledger
>     * I do inventory checks monthly to keep track of use of inventory
> 
> 
> My questions is: how do I account properly for the use of inventory?
> 
> The only way I found was to create a virtual customer and sell the used
> inventory to them after which I rebalance the income account with
> towards an expense account. I asked an account about this, and she said
> it was a strange construction. 
> Besides this, I don't seem to be able to get the numbers right for
> inventory use.
> 
> What is the proper sql-ledger way of doing this?
> 
> Thanks for any help,


I don't know if this is SL specific, but it seems that each card should
be a liability for the value put onto it.

Then when used it is a sale that is paid out of the liability.
Each of those sales consumes inventory.

If I read your process correctly it seems the product you are selling
(coffee) should be an assembly that uses coffee, creamer, flavorings,
sugar, etc so it ties back to the inventory and properly pulls inventory
into COGS for it. Maybe one assembly per way the product is prepared,
and input the sales from the machine into SL periodically -- daily or
otherwise. 

Re: [SL] Accounting for fuel inventory in a small power generator

[Jeff V. <jv...@ch...>]

On Thu, 2006-11-09 at 22:12 -0600, Oscar A. Valdez wrote:
> El jue, 09-11-2006 a las 21:49 -0600, Jeff Vian escribió:
> > On Thu, 2006-11-09 at 09:00 -0600, Oscar A. Valdez wrote:
> > > We are a small power generator that purchases fuel and converts it into
> > > electrical and heat energy for sale.
> > > 
> > > I've looked at the manual's section on Inventory, and it doesn't seem
> > > like I can have a fuel inventory and periodically consume it to produce
> > > energy for immediate sale (can't be inventoried). That would seem like a
> > > Job Costing or WIP functionality that doesn't seem to be there in
> > > SQL-Ledger.
> > > 
> > > Am I wrong?
> > > 
> > Just a thought from a layman. IANAA
> > 
> > Fuel used in operations is an expense item.  You may buy it, and have
> > some quantity on hand, but it is consumed as overhead in the production
> > of energy.  It should not be treated as inventory for this purpose.
> > 
> > Energy can be treated as a service, since it is not tangible inventory.
> > It can be sold by the unit, similar to service hours, and cannot be
> > stored. Invoicing goes to AR.
> 
> But what we do is transform fuel into electricity and heat. It's an
> industrial transformation. So fuel is our raw material, and electricity
> and heat our end products.

Deiter made the comment that it can be used as part of an assembly,
which would be the units of energy produced and sold.  As such, you buy
it, it goes into inventory, and as you sell the energy/heat it gets
consumed and the cost becomes part of the COGS.

I have a slight problem with that in that energy is not physical  and
cannot be stocked even though the fuel is physical.  However, the
concept seems proper. Cost of fuel is part of the cost of producing the
energy you sell.

Re: [SL] Accounting for fuel inventory in a small power generator

[Jeff V. <jv...@ch...>]

On Thu, 2006-11-09 at 22:12 -0600, Oscar A. Valdez wrote:
> El jue, 09-11-2006 a las 21:49 -0600, Jeff Vian escribi=C3=B3:
> > On Thu, 2006-11-09 at 09:00 -0600, Oscar A. Valdez wrote:
> > > We are a small power generator that purchases fuel and converts it =
into
> > > electrical and heat energy for sale.
> > >=20
> > > I've looked at the manual's section on Inventory, and it doesn't se=
em
> > > like I can have a fuel inventory and periodically consume it to pro=
duce
> > > energy for immediate sale (can't be inventoried). That would seem l=
ike a
> > > Job Costing or WIP functionality that doesn't seem to be there in
> > > SQL-Ledger.
> > >=20
> > > Am I wrong?
> > >=20
> > Just a thought from a layman. IANAA
> >=20
> > Fuel used in operations is an expense item.  You may buy it, and have
> > some quantity on hand, but it is consumed as overhead in the producti=
on
> > of energy.  It should not be treated as inventory for this purpose.
> >=20
> > Energy can be treated as a service, since it is not tangible inventor=
y.
> > It can be sold by the unit, similar to service hours, and cannot be
> > stored. Invoicing goes to AR.
>=20
> But what we do is transform fuel into electricity and heat. It's an
> industrial transformation. So fuel is our raw material, and electricity
> and heat our end products.

[SL] Indirect income and inventory managent

[Aschwin v. d. W. <asc...@bt...>]

Hi,

Here at work I am taking care of a fancy coffee-machine that uses a
cash-card system for payments, and I decided to use sql-ledger to keep
track of inventory and transactions. The idea is not to make profit on
coffee-sales, but to charge people only the costs involved.

But I have a problem accounting properly for my used inventory.

The sales process is as follows:
    * Cash cards are refilled once in a while and I receive money 
      for this. These transaction are nicely recorded in sql-ledger.
    * People use their cash cards to pay for coffee-drinks and the 
      machine keeps track of how many times each coffee option is 
      used. These transaction aren't recorded in sql-ledger even 
      though inventory is used, but no money is received.

The inventory process is as follows
    * Inventory is received from vendors and payments are recorded in 
      sql-ledger
    * I do inventory checks monthly to keep track of use of inventory


My questions is: how do I account properly for the use of inventory?

The only way I found was to create a virtual customer and sell the used
inventory to them after which I rebalance the income account with
towards an expense account. I asked an account about this, and she said
it was a strange construction. 
Besides this, I don't seem to be able to get the numbers right for
inventory use.

What is the proper sql-ledger way of doing this?

Thanks for any help,

-Aschwin

Re: [SL] Invoice with full details?

[Dr E. L. <el...@li...>]

I have noticed.

It happens extremely rarely. So the client gets two pages. So what
:-)-O? I'm more concerned that they pay the invoice :-)-O

Do you want to see my AR Aging Statement :-)-O?

el



on 11/10/06 2:28 AM Stroller said the following:

>> <%foreach number%>
>>    <%number%> &
>>    <%description%> &
>>    \ifthenelse{\lengthtest{<%subtotal%>pt<0pt}}{}{<%deliverydate%>} &
>>    <%qty%> &
>>    <%unit%> &
>>    \nprounddigits{2}\numprint{<%sellprice%>} &
>>    \nprounddigits{2}\numprint{<%discount%>} &
>>    <%linetotal%>\tabularnewline
>> <%end number%>
>> \end{longtable}
>=20
> If the last item comes at the very foot of the page, and the page =20
> breaks with only the lastfoot to display, is there any logic to =20
> prevent the head being shown at the top of the next page?
>=20
> I have not used your template verbatim - although it is quite =20
> beautiful, it is not quite my style of formatting, so I started again =20
> from scratch and have used yours only for reference.
>=20
> I have found one of my invoices has two pages.
> On the first is:
>=20
>    Part Description Price Quantity Amount
>    101  Fangle      =A31    3        =A33
>    237  Wonkle      =A32    1        =A32
>    ...
>    093  Chocolate   =A30.5  3        =A31.5
>=20
> and on the second is only:
>=20
>    Part Description Price Quantity Amount
>                           Total    =A36.5
>=20
> (I have laid out these examples so they make sense if viewed in a =20
> fixed-width font).
>=20
> I have been so impressed by your responses to my recent questions =20
> that I cannot believe that you have missed this, yet I cannot quickly =20
> see how you have solved this problem regarding invoices of a certain =20
> length.
>=20
> Stroller.


--=20
Dr. Eberhard W. Lisse  \        / Obstetrician & Gynaecologist (Saar)
el...@li... el108-ARIN / *     |   Telephone: +264 81 124 6733 (cell)
PO Box 8421             \     /   Please do NOT email to this address
Bachbrecht, Namibia     ;____/        if it is DNS related in ANY way