Modifying the AX 2012 Customer or Vendor Aging Reports

By Becky Newell | January 28, 2014

I recently modified the customer aging report in AX 2012 and I can tell you the report is difficult to follow.  There are several class hierarchies and temp tables involved and it is easy to get lost in them.  While making my way through the aging puzzle, I took the notes below.  I hope you find them valuable if you are ever making modifications to the customer or vendor aging reports.  Enjoy!

In the class and method CustAgingReportDP\processReport on line 85 there is this line:

custVendBalanceList.calculateDetailsForMultipe(qr, contract.parmIncludeAmountCur());

The line above calls out to the CustBalanceList class which inherits from CustVendBalanceList.  In method calculateDetailsForMultiple in CustBalanceList on line 5 there is this line:

custVendAgingCalculateTmp = agingCalculation.process(_queryRun);

That lines calls out to the process method in the CustVendAgingCalculation class.  The process method is a driver method in which the data is collected that is later displayed in the report.  The process method is a good place to set your breakpoints.  On line 14 of the CustVendAgingCalculation\process method it collects all of the customers (or vendors) the report is going to look at.  This is the line of interest:


On line 20 of CustVendAgingCalculation\process it grabs the open and closed transactions that will be displayed in the report.  If you look at the CustVendAgingCalculation\selectTransactions method you will see it has two separate calls:



Both the selectClosedTransactions and selectOpenTransactions methods query the CustVendTrans and CustVendTransOpen tables for data.  The methods insert what they find into a CustVendAgingProcessingTmp table.  The details for the transactions are collected in the CustVendAgingProcessingDetailsTmp table and then both the CustVendAgingProcessingTmp and CustVendAgingProcessingDetailsTmp tables are combined into a single CustVendAgingCalculatedTmp temp table in the CustVendAgingCalculation\process method.  Once everything has been pulled together, the CustVendAgingCalculatedTmp table is returned to the CustBalanceList\calculateDetailsForMultiple method.

Next in the CustBalanceList\calculateDetailsForMultiple method the insertIntoTmpAccountSum method is called.  In the insertIntoTmpAccountSum method the contents of the CustVendAgingCalculatedTmp table are inserted into a CustTmpAccountSum temp table.  At the very end of the CustBalanceList\insertIntoTmpAccountSum method the TmpAccountSum is an instance of the AccountSumMap.  The map is set equal to the CustTmpAccountSum table.  The mappings on the AccountSumMap map translate the fields in the CustTmpAccountSum table to an instance of the TmpAccountSum temp table.

The TmpAccountSum table is then used by the CustAgingReportDP\processReport method on line 90 with this call:


The contents of the TmpAccountSum are inserted into a CustAgingReportTmp table and this temp table is what is returned to the SSRS report design.

Start the Conversation

It’s our mission to help clients win. We’d love to talk to you about the right business solutions to help you achieve your goals.

Subscribe To Our Blog

Sign up to get periodic updates on the latest posts.

Thank you for subscribing!