Multi-company installations can lead to failures in the cube based reports

During a staged AX 2012 deployment on a multi-national, multi-company it is normal to create a new AX company.  But did you know that some missing setup in that new company could mean that the Live companies loose their reports.  The MDX queries within the reports require that certain Ledger parameters are set and if they are missing then the report shows “No data available”.

Any MDX query that uses the “Accounting Currency” setting in the Ledger, I think this is most reports, will fail if this setting is missing.  I also mean the DAT company.

The new company must have the Chart of Accounts, the Accounting currency AND exchange rates setup for that currency.  The MDX queries are looking directly at exchange rates and currencies in the reports and if they do not exist the query does not cope with it.

The lesson here is be sure you are ready to complete the setup in the Live environment.

Customer reconciliation report AX 2012

When is a report not a report?  When you get a data definition language error with truncation issues of course.

When populating a reporting temp table the EDT’s must be the same, the original transaction table EDT must have the same properties as the temporary table EDT’s.  This is fairly obvious but in the Customer reconciliation report this fails because of a mismatch.

The reporting temporary table is CustLedgerReconciliationReportTmp and the Name EDT is 60 char, the Name is coming from the DirPartyTable which is 100 Char.  99% percent of the time it works, but as soon as the customer name is longer than 60 Char it fails with a truncation error.

Solution is easy and know you know the issue I’m sure you can fix it!

Path to run the report is General Ledger > Reports > Reconciliation > Customer > Customer.