Page 1 of 1

EFT Remittance Advice

PostPosted: Wed Dec 09, 2015 1:19 pm
by Nina Tulic
Hi Guys,

We need to modify the MNT80102 - EFT Remittance Advice report.
Are we able to replace the base tables with our own Stored Procedure or view? (Like for Report MNT30000 - Invoice.rpt) Or do we need to keep the existing tables?

What and how are the parameters sent to the report?

Thanks
Nina

Re: EFT Remittance Advice

PostPosted: Wed Dec 09, 2015 1:48 pm
by Scott.Pearce
You can do whatever you like to the report and underlying data-source. We just ask that you make a COPY of the standard one, and modify that - otherwise your changes will be overwritten by us during upgrades.

As for parameters, in the case of the Creditor EFT/Cheque Payments form, when printing it will set the report's selection formula to be "{CR_Trans.ChequeRunID} = <Whatever the current on-screen batch BatchPayID value is>". This means that you MUST have the CR_Trans table linked into the report. So, if you wanted to use a stored procedure for the report, write your stored procedure such that one of it's return fields is CR_Trans.ChequeRunID. Then, in Crystal you can link the CR_Trans table to your stored proc on the ChequeRunID field. Then the selection formula Jiwa pushes into the report at print time will be valid.

Re: EFT Remittance Advice  Topic is solved

PostPosted: Wed Dec 09, 2015 1:52 pm
by Scott.Pearce
Upon further reflection, I'm not sure how efficient doing the above would be - you will have to test on a large database. I think I'll log a bug to add some nice stored proc parameter support to that particular form in any case. I'll edit this post with the bug number.

EDIT: Logged as enhancement 12343

Re: EFT Remittance Advice

PostPosted: Thu Dec 10, 2015 11:58 am
by Nina Tulic
Thanks Scott.

Nina