(773) 384-9264  

Customer Feedback
  • "It’s been really nice working with you, Jamie and Ruby! Thank you for your continued support to Frank, Rimerman Consulting."

    Beverly MCSM (GP Partner)
  • "Thanks for the late-night support the other night!... Client was operating as it should this morning!   WOOO HOOOO !"

    Maureen ACAE (GP Partner)
  • "Have I told Alba-Spectrum this year yet how F A S T the newsletter selection is now ???? Wow. Thank you very much!"

    Dennis Westbrook
  • "We were successful last night in completing the production deployment of Terminations WF. Ricardo was fantastic and we could not have done this without him"

    Tawna KProject Manager (Credit Management)
  • "[We are] so grateful for Jeff’s help, and Jeff has been so good to...ZTrim in all of his support."

    John ECFO (Agricultural Ingredient Technology)
  • "First off, thanks for all the great suggestions. I’ll let you know what we find out. Many thanks for your help"

    Mark BDeveloper (Telephone Company)
  • "I will e-mail you back to let you know I was successful with HJE – which I expect to be. I really appreciate how you helped me."

    Michele DurkinConsultant (GP Partner)
  • "...thank you both for taking some time out to help me troubleshoot the issue of creating a project directly into the GP tables without the benefit of using the web services."

    Jesse CPrincipal (GP Partner)
  • "For example, when an AE calls to confirm rates, there’s not a 30 second pause waiting for the billing schedule to open. It’s absolutely immediate, literally, click, click, click. It’s a huge difference."

    Vince FCredit Manager (Media Data Service)
  • "So far everything seems to be working fine. We have had it in production now for almost a month and have not experienced any problems."

    Mark MFinance Manager (Custom Woodwork)
  • "Alba will always be my choice for quality innovation on ANY project you put in their lap from websites to Great Plains implementations, customizations and people who think 'outside the box'. "

    Robert DCEO
  • "Rod, your team’s flexibility and quality of service have been appreciated."

    Nicholas NController (Financial Trading)
  • "I most heartily and sincerely recommend him and his firm for any software implementation task."

    John PCFO (Tourism Association)
  • "[the] team delivered several enhancements to Great Plains, significantly improving our sales order entry process, shipment routing, and handling of catch-weight items."

    Eddie HPresident (Food Products)
  • "You have come very highly recommended by other companies. I have been impressed with your professionalism and attention to detail."

    Timothy CPresident (Uniform Manufacture)
  • "I am very happy that Andrew was able to fix our invoice system. Your company is very professional and performs excellent service."

    Allen ZCFO (Oil Company)
  • "I don't know who your company president is, but you guys did great job and I hope he/she sees this email."

    Nathan M.Finance (Marketing Communications)
  • "I heartily recommend Alba to any developer or end user seeking to make the most of their GP investment."

    Brett GPresident (Software Development)
  • "Thank you for all your patience and hard work getting this all processed. Here at Friedr Dick Corp we are looking forward to a wonderful professional relationship."

    Jill DAccounting Manager (Home Furnishings)
  • "I think we are going to be a great team working forward on the Miami project."

    Jesse CPrincipal (GP Partner)
  • "As usual, superb product and service!! Everything is working great and all my users love the modification. Thanks again!"

    Michael LController (Healthcare Storage)
  • "[W]e thought your product GP Posting Server was the better solution. The interface is better, it is easier to understand, and there are more options considering the auto transfer feature. We compared it to the Envisage Post Master Enterprise software."

    Tom BSenior IT Administrator (Medical Implements Company)

How to Rebuild the Data Mart Integration in Management Reporter 2012


Management Reporter is a real-time financial reporting application for Dynamics ERP systems (e.g. Dynamics SL, AX and GP) and is the replacement of Microsoft FRx for 64-bit environments.

The Data Mart is the new method for integrating financial information from the Dynamics ERP with Management Reporter 2012.  It was introduced in MR Roll-Up 3 and is the preferred method of integration moving forward.  The (Data Mart) stores summarized numbers in its own SQL database instead of reaching into the GP database each time unlike the old “Legacy” method.  This option improves performance when generating reports in Management Reporter 2012 and supports a greater level of integration with Dynamics ERP systems.


OS: Windows Server 2008 R2

GP: Dynamics GP 2013 SP1

MR Version: Management Reporter 2012 RU7

SQL Server: SQL 2012 with AlwaysOn Availability Group enabled


In some cases, there are missing financial information (e.g. missing accounts, account format, etc.) or incorrect values in MR reports.  This issue may happen if there was an error in the flow of data from GP to MR and DDM database due to timeouts in the SQL process or the Data Mart integration triggers has not yet fired off.


  1. Log off all users from Management Reporter. These steps ideally are performed during off-peak hours.

  2. Verify that the domain user who is performing the procedure has the correct permissions (e.g. “sa” or “W2K\svc_mrsvr”) on the SQL server and to the new database.

  3. Make sure that the Data Mart (e.g. “DDM”) database is removed from the Availability Databases in SQL 2012 since the steps below will require you to delete and recreate the database.


    (Note: Notice how the DDM database above does not indicate it is “synchronized”.  This means that it is not added to the Availability Databases for AlwaysOn mirroring.)

  4. Start the Management Reporter 2012 Configuration Console. (Click on Start, point to All Programs then click Microsoft Dynamics, clickManagement Reporter 2012, click Configuration Console).

  5. Record the name of the database listed under the Database connection heading. The database name will be listed after the SQL server name. For example: SQLServer (ManagementReporter)

  6. Under ERP Integrations on the left pane, highlight the Data Mart integration being used and disable the integration by clicking the Disable Integration button.

    Management Reporter Configuration Console

    (Note: In the screenshot above, a “Legacy” integration is also configured.  There is no need to delete this as it will get repopulated after the ERP Integration has been rebuilt.)

  7. Click Remove to remove the ERP integration.

  8. Click Yes to the prompt “Are you sure you want to remove the ERP Integration?”.

  9.  In the Management Reporter 2012 Configuration Console, click Management Reporter Services

    Management Reporter Configuration Console

    (Note: In the screenshot above, assume that the Data Mart integration has already been removed)

  10. Record the name of the Service Account that is used then exit the Management Reporter 2012 Configuration Console.

  11. In the navigation bar, click Management Reporter Services.

  12. Click Remove Process Service.

  13. Click Yes to the prompt “Are you sure you want to remove ‘Management Reporter 2012 Process Service?”.

  14. Click Remove Application Service.

  15. Click Yes to the prompt “Are you sure you want to remove ‘Management Reporter 2012 Application Service?”.

  16. Login to SQL Server Management Studio and access the SQL instance where the database recorded earlier in step 5.

  17. Delete the “DDM” database by right-clicking on it and clicking Delete.

  18. In the Management Reporter Configuration Console, re-install the MR Process and Application services and add the DDM integration by going to File and click Configure.

    Configure Management Reporter

    (Note: In the screenshot above, I am only re-installing the Data Mart since I already have an existing Management Reporter Application Service and Management Reporter Process Service.)

  19. In the Configure Management Reporter window, install the Management Reporter server components and put a check next to:

    a.       Management Reporter Application Service – Controls access to Management Reporter data and provides connectivity to ERP systems.

    b.      Add Microsoft Dynamics GP Data Mart – Installs the DDM database in the specified SQL instance to integrate with the GP company.

    c.       Management Reporter Process Service – Generates the reports that are created and queued by the Management Reporter client component.

  20. Enter the following information in the Service Account area:

    a.       Select type of account that you are using for the Service account in the Account field.

    b.      Enter the domain, user name, and password for the Service account recorded in step 10 above.

  21. To configure the application service, enter the following information in the Application Service area:

    a.       Accept the default port for the web application to use, or enter another port.

    b.      To configure Windows firewall settings automatically, select Open this port in the Windows firewall. If you are using a different type of firewall, you must open the port manually.

  22. Under Database Configuration, select the Connect to an existing database check box.

  23. In the Database Server field, select the existing “Management Reporter” database.

  24. Select an authentication option for the Management Reporter Administrator account:

    a.      To use your current credentials, select Use Windows authentication.

    b.       To use SQL authentication, select Use SQL authentication, and then enter the domain, user name, and password of the Management Reporter Administrator account.

  25. Configure the data mart integration by using the appropriate credentials below:

    Configure Management Reporter

    (Note: In the screenshot above, I am only re-adding the Data Mart integration since I already have existing MR Application and Process Services.Make sure to use the existing DYNAMICS database for the Dynamics GP connection information and create a new Data Mart database for the Data Mart connection. In my example, I changed the default Database name from “ManagementReporterDM” to “DDM”.)

    ERP integration

    Required information

    Microsoft Dynamics GP Data Mart

    Dynamics GP Connection Information

    ·Database server– The name of the server that hosts Microsoft Dynamics GP.

    ·User nameandpasswordof a user account that has permissions to connect to Microsoft Dynamics GP.

    ·Database– The name of the Microsoft Dynamics GP system database to connect to “DYNAMICS”.

    Data Mart Connection Information

    ·(Data mart) Database server– The server where the data mart database is located.

    ·User nameandpasswordof the account that is used to create the data mart database. Select Use Windows authentication to use your current credentials.

    ·(Data mart) Database– The default name of the data mart database to connect to is “ManagementReporterDM”. This can be changed.


  26. In the Ready to Configure window, review the data integration information, and then click Configure.

  27. When a message is displayed that indicates that the data integration has been successfully configured, click Close. (Note: If you use a data mart integration for Microsoft Dynamics GP, company information is imported automatically)

  28. In the Management Reporter 2012 Configuration Console, verify that the Data Mart (DDM) (and Legacy integration if applicable) is already configured.

  29. Click Management Reporter Services and restart the Management Reporter 2012 Application Service and Management Reporter 2012 Process Service.  Verify that the services display a status of Running.

  30. Click the ERP Integrations on the left hand side and highlight the Data Mart integration you just configured.

  31. Click Enable Integration to allow initiate the integration of financial data from your Dynamics GP company with the newly created DDM database.  This way, all current financial information will refresh the DDM database and update the MR reports.

  32. Before re-adding databases back to the Availability Databases in SQL 2012, you must satisfy the following requirements:

    a.       Recovery Model must be set to “FULL”

    b.      A Full database backup has been created

Level of Usefulness

In circumstances where financial reporting is critical to the client, these steps prove to be invaluable in making sure that Management Reporter 2012 has up-to-date GP information.