[freeside-devel] A minor change to support adding referrals after the fact

[Dave Burgess]

> applied.  in the future it would help to include pathnames in your diff. 
> there's multiple files named "cust_main.cgi".  thanks. 

Sorry.  I keep forgetting to 'pop up' before I do the diff.

While I have your attention, I'm trying to decide the 'best' way to do 
something.  I am working on adding ACH transactions to the system.  Our
ACH system uses a CDF format for import into their ACH program.  They 
claim that their software is the only way they will allow access, but 
they do allow for imports from a file.  So, I'm going to build an ACH
batch that will be imported into the existing software from the bank
which will then be transmitted, via modem, to the bank.

The problem I'm running into is that I'm going to require at least
two 'batches':  at a minimum, one for credit cards and one for ACH
transactions.  Tele-check transactions will probably be processed
like credit cards, but I'm not sure yet (since we don't actually
do that).  Most of the code I've written so far assumes that if
there are no check numbers available, the transaction should be
processed through ACH.  The guy from the bank thought that would
be an interesting way to do it...  Regardless, I'm in a quandry.
I need to decide if I want to start up my own database table (with
a structure almost identical to the cust_pay_batch table) or if I
should add a destination/flavor flag to the existing cust_pay_batch
table.

Think about it and let me know which way you'd be most comfortable.

Also, on the SSAN front: I added a little bit of code to the cust_main.pm
file to allow SSAN to be entered in the system unless there is a 
'user_nossan' flag in the conf directory.  The display suppresses it either
way right now.  The reason I went to the trouble is that the Bank suggests
using the SSAN as the customer identifier.  While that's dicey for the ISP,
it's OK for the bank (financial transactions are tracked by SSAN) when ACH
is involved.  Besides, I wanted to keep a way for people to use SSAN if they
needed to.

What else has he done? you might ask....  

- I added some /  entries to some of the cust_main.cgi entries
so that the table would look like a table on the printer.  On the
screen, it doesn't matter much, but it looks odd to have the
separators disappear when you are looking at a table.

- I also added some of these to the table builder in search/cust_main.cgi.

- I changed the default dates on the 'new customer' screen.  The system now
uses the current date from the server and sets the various entries to
'reasonable' values.  The Credit Card entry starts out 12 months from now 
(it's halfway through a 2 year period and will be right about 4% of the time).
The Complimentary entry expires in 1 year; the Bill and ACH entries expire
in 2037.  I found a couple of places in the system where the year 2001 is 
hardcoded in.  I'll see if I can't find them and fix them.

Well, that's enough for the 6 hours I spent tonight.  I'm having trouble 
keeping the patches segreagated, especially when I work on three or four 
trouble tickets from the book keeper and receptionist.  I hope you can
forgive me for lumping a lot of these patch sets together.

Dave

Dave