Re: BACSTEL-IP for supplier payments

Dave,

I'm not familiar with the new Geac BACSTEL-IP offering, having 
disconnected myself from Geac a couple of years ago.  But since they've 
had a day to answer, I'll hazard some guesses for you.  I'll bet that 
phantom BACS User Number is 907049, my old RBS testing number.  The 
crucial file is BACSF1, and I suspect you've got a member called A907049 
in there somewhere.  I used to ship it out with the software, so I had 
some test data ready for an onsite Unattended Test Phase 3.

Take a look at the members [DSPFD FILE(OSLBPF2/BACSF1) TYPE(*MBRLIST)] and 
see what you've got.  And then use RMVM to clean out any unwanted members.

Hope this helps!


Mike Waite 

system21-bounces@xxxxxxxxxxxx wrote on 01/11/2005 16:10:27:

> I have installed the BP application PTFs for sending supplier payments
> via the Geac BACSTEL-IP/EigerPay solution. When I want to send a payment
> file over to EigerPay, I can now see  payment files for every company on
> my system, including the JBA test companies, and a "phantom" BACS user
> number that comes from I don't know where. Has anyone else got
> BACSTEL-IP working for supplier payments in a multi-company environment
> without having all the payment files for every company displayed when
> you want to send just the current company's payments? Does anyone else
> have the phantom BACS user number problem? If so, what, if any, was the
> solution?
> 
> 
> David Dewick 
> Information Technology Manager 
> Darcast Crankshafts Limited