Adding field to Accounts Receivable Aging Report - SLOW

Hi,

I am working on editing the Accounts Receivable Aging Report in CSI10. With our other reports we use secondary collections without issue. In this case, I have added my secondary collection to the report viewer but it takes forever to run. It does complete successfully though and looks correct.

Without the secondary collection it takes about 20 seconds to run. With the secondary collection it takes 9 minutes for a 15 page report. I know the inv_hdr table is large, however we have other reports with larger datasets without issue.

Anyone else experience this issue?

Thanks
Ryan

Find more posts tagged with

Syteline Development

Accepted answers

All comments

mtolliver

Have you been able to make a working version of your aging report in CSI 10? We are on-prem and used a custom dataview from another community member that worked in 9 and converted to 10, however we are looking to uplift to the latest version and we are getting errors with the Rpt_AccountsReceivableAgingSp that is used for populate our dataview. We just need a clean export of the aging data and every version of the new vendor version seems to be messy. Looking for some suggestions or guidance on what others do or use for this report.

Ryan Pukanski

Hi,

Yes, we got it to work fine. We use the standard Rpt_AccountsReceiveableAginSp method and run it against a dataview. We use the same report form and just added a dataview button to it.

DataviewParm1 = DataViewName=_VOLRPT_ARAging,InputParameter1=V(AgingDateOffset),InputParameter2=V(CutoffDateOffset),InputParameter3=V(DateNullVar),InputParameter4=V(DateNullVar),InputParameter5=V(StatementCycles),InputParameter6=V(ShowAct),InputParameter7=V(SalePersonStarting),InputParameter8=V(SalePersonEnding),InputParameter9=V(CustomerStarting),InputParameter10=V(CustomerEnding),InputParameter11=V(NameStarting),InputParameter12=V(NameEnding),InputParameter13=V(CurrencyCodeStarting),InputParameter14=V(CurrencyCodeEnding),InputParameter15=V(PrintZeroBalanceCustomers),InputParameter16=V(CreditHold),InputParameter17=V(PrintCreditBalanceCustomers),InputParameter18=V(SumCorpCust),InputParameter19=V(Translate),InputParameter20=V(UseHist),InputParameter21=V(PrintPostedTransaction),InputParameter22=V(PrintOpenPayments),InputParameter23=V(HidePaidInvOlderThan),InputParameter24=V(SortByCurrency),InputParameter25=V(SortBy),InputParameter26=V(AgingBuckets),InputParameter27=V(AgingBasis),InputParameter28=V(Days1),InputParameter29=V(Days1Detail),InputParameter30=V(Days2),InputParameter31=V(Days2Detail),InputParameter32=V(Days3),InputParameter33=V(Days3Detail),InputParameter34=V(Days4),InputParameter35=V(Days4Detail),InputParameter36=V(Days5),InputParameter37=V(Days5Detail),InputParameter38=V(SiteGroup),InputParameter39=V(DisplayHeader),InputParameter40=V(ConsolidateCustomers),InputParameter41=V(IncludeEstCurrGainLossAmtsInTotals),InputParameter42=V(Parm_Site),InputParameter43=NEWGUID()

mtolliver

Oh wow, this is great! I was dreading re-creating this from scratch - do you mind sharing the XML for the dataview itself? If not I think I can tweak it to accept these parameters.

Ryan Pukanski

Send me a PM and I can get that over to you.

Copyright © 2025 Infor. All rights reserved.