Collections report error

OpenEMR Development
1

aperezcrespo wrote on Thursday, January 29, 2009:

Hello

When I try getting a collections report I always get this error message

ERROR: column customer.address1 does not exist LINE 1: …ar.shipvia, customer.id AS custid, customer.name, customer.a… ^: SELECT ar.id, ar.invnumber, ar.duedate, ar.amount, ar.paid, ar.intnotes, ar.notes, ar.shipvia, customer.id AS custid, customer.name, customer.address1, customer.city, customer.state, customer.zipcode, customer.phone FROM ar JOIN customer ON customer.id = ar.customer_id WHERE ( 1 = 1 ) AND ar.amount != ar.paid ORDER BY ar.invnumber

Any Ideas?

Thanks

2

aperezcrespo wrote on Thursday, February 05, 2009:

I did a different install but this time I configured with internal AR.

It works fine with internal AR but not with SQL-Ledger.

Unfortunately some of my clients want to keep the SQL-Ledger integration.

Thanks

3

cfapress wrote on Friday, February 06, 2009:

I can’t give you the definitive answer but I believe that your clients who want to continue with SQL-Ledger will need to remain at v2.8.3 of OpenEMR. The built-in AR in version 2.9 might create a conflict with an external SQL Ledger connection.

Jason

4

aperezcrespo wrote on Friday, February 06, 2009:

Hi Jason

Actually both work rather well.  The use of one or the other is an option in globals.php.
SQL-Ledger was still available in 2.9.0 released on Aug 7.  Rods implementation of AR was released into current CVS on Oct 29.
Rod also developed  an SL to AR migration script.  Currently all works fine (I even use the current version of SQL-Ledger with no problems)  except the collections report.  That seems to be the only thing currently broken with SQL-Ledger.

Alfonso

5

sunsetsystems wrote on Friday, February 06, 2009:

This looks like an incompatibility with SQL-Ledger 2.8.x.  It works with 2.6.x.

I’ll put in on the list to fix, but I really advise against using SQL-Ledger any more – the interface is too fragile.  There are better ways to interact with accounting systems.

Rod
www.sunsetsystems.com

6

aperezcrespo wrote on Friday, February 06, 2009:

Hi Rod

Please do point out some of the better ways to interact with accounting systems.  AR is cool but full accounting is a real nice upsell.

My clients really like the fact that they don’t have to re-enter these transactions into an accounting system.

But building a full accounting package for OEMR is probably out of scope.

Thanks

7

sunsetsystems wrote on Saturday, February 07, 2009:

I think it’s best to enter OpenEMR data into the accounting system at a summary level.  If you want more detail than is practical to enter manually on a daily or monthly basis, then an export script that produces data acceptable to the accounting system would need to be created.

The point is, OpenEMR has a lot of tools to handle A/R and it’s best to use them and (if desired) build on them.

Rod
www.sunsetsystems.com