Customer Success Story: Blu Dot

ABOUT COMPANY: 
Blu Dot was born in 1997. Their goal is to bring good design to as many people as possible. That means creating products that are useful, affordable and desirable. To make that happen, their design process is founded on collaboration. Blu Dot likes to think that the form is almost inevitable, a by-product of the process. Their job is simply to help design emerge as beautifully and as efficiently as possible.

Blu_Dot_066

BUSINESS SITUATION: 
Blu Dot’s business was growing faster than their manual systems would allow, so they turned to InterDyn BMI for technology solutions that would scale with their business. Since then, revenues have grown from $7M to $80M.

THE SOLUTION: 
InterDyn BMI worked collaboratively with Blu Dot to provide a Microsoft based technology infrastructure that would grow with their business. The solution included Microsoft Dynamics GP, SQL Server, Exchange and Windows Desktop. The solution platform also supports robust companion products to enhance their business and the ability to integrate with other business systems and applications.

InterDyn BMI has consistently met and exceeded the expectations of our growing company’s demands. From supporting overseas offices and retail stores, to our recent office and warehouse move, they have always provided professional service with technical consultants who are knowledgeable, productive, and willing to go the extra mile to resolve issues. It is a tremendous asset to our company to work with a team of people who we can trust to support our IT requirements.”

PROVEN RESULTS:

  • Decreased report creation time by more than 75%
  • Enhanced distribution power and functionality to drive growth
  • Became greener by reducing paper usage by 25%
  • Moved focus to core values and growing the business rather than on low-value administrative tasks
  • Achieved GAAP compliance
Advertisements

Take Note of This New GP 2015 Feature

Even the smallest change or enhancement to an ERP solution can make a world of difference, especially when the upgrade is overdue. One notable feature of Microsoft Dynamics GP 2015 is the Payment Terms functionality, which has been relatively unchanged in the previous three versions.

Let us look at the Payment Terms window in GP 2013:

Payment Terms window in GP 2013

The date options are restricted to the following:

  • Net Days
  • Date
  • EOM
  • None
  • Next Month

While this may have not been a terrible limitation, it did make setting up some of the more unusual terms codes practically impossible. Fortunately, with the release of GP 2015 came a new feature that allows more flexibility for due-date and discount-date calculation as well as the ability to calculate terms codes in the setup window. This also helps users validate that the right settings are in place.

The due date can now be calculated from the transaction date or from the discount date, with the option to include additional dates to the transaction date option.

In addition to what was available with GP 2013, the due-date selection options now include:

  • Months
  • Month/Day (select the specific month & day that transaction is due)
  • Annual

A “Calculate” button has also been added to the window so that users can immediately check the terms-code setup rather than having to open up a separate transaction window.

GP2015 Calculate Button

If the calculation isn’t correct the first time around, any changes can be made by keeping the Payment Terms Example window open and updating the payment-term setting in the Payment Terms Setup window. At the end, simply click on the redisplay button.  Now with GP 2015, making minor, incremental changes to the terms code just became quite simple!

What will your existing terms code look like after the upgrade?  Users may need to evaluate their terms codes after the upgrade to GP 2015. The following chart demonstrates the expected path of your data to the new table layout.

GP2015 Table Layout

Download Management Reporter 2012 CU9 Today!

Management Reporter 2012 CU9 has been posted for download!

This release contains enhancements to the Management Reporter Web Viewer around opening and refreshing reports along with additional troubleshooting information in the Configuration Console related to data issues in the ERP.

Here’s a summary of the new Management Reporter CU9 features:

•View a list of previous month’s reports and open them in the web viewer

•Refresh a report in the web viewer

•Publish a report from the web viewer

•Headers and footers are shown by default in the web viewer

•Enhanced data detection in the Configuration Console

•Support for SQL Server 2014

•Additional fixes for product defects

You can find the download for Management Reporter CU9 here: https://mbs.microsoft.com/customersource/northamerica/MR/downloads/service-packs/MROverview

Questions? Contacts us today!

 

Source

How To Link an External Spreadsheet to a Management Reporter Report

Have you ever wondered how you could link an External Spreadsheet to a Management Reporter report?

The following is an example of how to get your report to present GP and Excel data from two different spreadsheets.

The two screen shots below reflects the Excel spreadsheet data we want to use. This is a Management Reporter report.

EXCEL SPREADSHEET – Sheet 1:

Excel Spreadsheet 1

EXCEL SPREADSHEET – Sheet 2:

Excel Spreadsheet 2

To build the report, you may want to build the components in the following order – Row, Tree, Column and the Report Definition.
ROW DEFINITION:

Add the Row link to the Row format.  Edit>Row Link.  In the Row link window you can add more than Excel file link.

Row Links

If the Excel file that you are linking to has multiple columns that represent different periods (for example, a worksheet that has a detailed, 12-month Budget Forecast), you can use the /CPO (Column Period Offset) option to match the accounting periods in the Column Definition with the appropriate columns in the Excel worksheet.

You can use this technique with either the Combined Worksheet link or the Separate Worksheet link.
To use the /CPO option, in the row definition, type the cell address that points one column to the left of the first period (column). Then, add the /CPO option at the end of the cell address.

CPO

TREE FORMAT:

Add unit names to the tree that will define the Spreadsheet Information to review.  You will need to assign a Row Definition before you can select the Worksheet link.  The Worksheet Link Column (G) will allow you to select any link you’ve defined in the Row format.

Tree Format

COLUMN FORMAT:

Create a column type WKS and then in the Report Unit Field select the Summary Unit you created in your Reporting Tree definition.

Column Format

REPORT DEFINITION:

Create you Report Definition using your new Row, Tree and Column.  You will want to make sure you name the Use Row Definition from the Reporting Tree Check Box.

Report Definition

 

REPORT GENERATED:

Report Generated

Report Generated 2

Visit our website to learn more about Microsoft Dynamics GP and our full product line.

Contact InterDyn BMI today!

Read why InterDyn BMI is holding off on using the Management Reporter Data Mart for Dynamics GP

By Lorna Link, GP Product Manager

Starting with RU3, Management Reporter 2012 includes a new “Data Mart” data provider for Dynamics GP in addition to the one included with earlier versions, which is now referred to as the “Legacy Provider.”

The Legacy method pulls numbers direct from Dynamics GP tables and calculates balances on the fly. This method can be slow especially reporting against multiple companies.

The Data Mart method stores financial information already summarized in its own SQL database. Reports generated using the Data Mart are pulling those summarized numbers instead of calculating them, improving performance for a large quantity of data.

This integration is constantly running. When data changes in Dynamics GP those changes are rolling down in the Data Mart database.

With a few exceptions, Data Mart is Microsoft’s preferred data provider for Dynamics GP, and Microsoft is planning to discontinue Legacy, but the Data Mart has issues that need to be fixed.

Reporting from ‘Legacy’ is one Management Reporter company, Reporting from the Data Mart requires another Management Reporter company

InterDyn BMI has observed issues with the Data Mart data provider, where Management Reporter reports are not returning the data or behaving in a way that a user is expecting. There are more problems with every roll up and they seem to be data mart related, for example:

• Errors during generation
• Missing data on financial reports
• There is a recognized bug with GP2013 with multi-currency is duplicating entries with the Data Mart and Microsoft has said this won’t be fixed until early 2014.
• There is also a bug with the header descriptions not working.
• Issues with analytical accounting reports missing financial data.

RU7 was recently released, but did not directly address all of these issue. We anticipate the RU8 will resolve many of these issue. RU8 should be release in early 2014. At that time we will reevaluate the use of Data Mart for Dynamics GP.

If a client ends up needing the Data Mart or we need to move them to the Data Mart once all issues have been resolved, the time to switch to Legacy is minimal in comparison to the potential problems that would be incurred in the short term with the Data Mart. We would estimate 1-2 hours to switch from Legacy to Data Mart, as estimated below:

1. We would need to remove Legacy, which takes less than a minute.
2. Install the Data Mart, which takes 15 – 20 minutes.
3. Point reports to the different company – up to an hour depending upon the quantity of reports.

Our plan until February 2014 is to install only Legacy for both new implementations and upgrades. When RU8 has been released, the issues are expected to be resolved we’ll resume using the Data Mart unless there is a specific business need to install the Data Mart. We’ll continue to be mindful of the installation recommendations when customers are using Analytical Accounting and Multi Currency.

Visit our website to learn more about Microsoft Dynamics GP and our full product line.

Contact InterDyn BMI today!

Management Reporter and Professional Services Tools Library Fiscal Year Change

Written by Lorna Link, GP Product Manager

An interesting find from Brian Bell, GP Implementation Consultant – A client just reset their GP fiscal year end from 3/31 to 12/31 and found that Management Reporter doesn’t follow the same rules as GP.

We used a 9 month stub year GP’s fiscal year label went from 1996 to 1995 for the oldest historical year.  Management Reporter CALCULATES its fiscal year label from the last date of each fiscal year, so it’s using 1996 still as the oldest fiscal year and not using GP’s fiscal year labels at this point.

You can modify the FiscalCalendarView by running the following script against the DDM database:

–//////////////////////////////////
–Script start
–//////////////////////////////////

SET ANSI_NULLS ON GO
SET QUOTED_IDENTIFIER ON GO
ALTER VIEW [dbo].[FiscalCalendarView] AS SELECT TOP 100000 RANK() OVER(ORDER BY PER.OrganizationId, FY.Id, PER.Starts, PER.Ends) as PeriodSequenceNumber,
RANK() OVER(PARTITION BY FY.id, PER.OrganizationId ORDER BY PER.Starts) as PeriodNumber, PER.Id, PER.Starts as PeriodStart, PER.Ends as PeriodEnd, FY.Starts as YearStart, FY.Ends as YearEnd, CAST((SELECT MIN(Years.Name) FROM FiscalYear Years WHERE Years.OrganizationId = FY.OrganizationId) + DENSE_RANK() OVER(PARTITION BY PER.OrganizationId ORDER BY FY.Starts) – 1 AS Int) As FiscalYear, IsHistorical, PER.IsClosed, PER.OrganizationId FROM Period PER INNER JOIN FiscalYear FY ON PER.FiscalYearId = FY.Id AND PER.OrganizationId = FY.OrganizationId ORDER BY PER.Starts GO

–//////////////////////////////////
–Script end
–//////////////////////////////////

Note that if you have to re-create the DDM database for any reason, you will need to re-run the script provided above.

Visit our website to learn more about Microsoft Dynamics GP and our full product line.

Contact InterDyn BMI today!

TSA Set Up Roll Down Bug

A client recently asked us if it was ok to change the TSA setting on a deduction code that had history. Two of our seasoned Payroll consultants both said “no”, and that if there is history no change can be made in GP to deduction codes with history.

The client changed the TSA flag with their setup and rolled down the setting change from the deduction code setup window and the TSA change was reflected in the employee’s next check. The new TSA setting does not reflect properly in the Employee Deduction Maintenance window.

The screen shots below show the impact to changing the TSA settings at the setup level of a deduction reflecting that is does unmark the TXSHANTY field in the database while leaving the checkboxes marked on the employee deduction card.

Employee deduction card and the SQL query after rolling down the change at the setup level:

TSAblog1

(Click on image to view larger).

TSAblog2

The situation was reported to Microsoft and they have provided workaround scripts until a fix can be included in a service pack for GP2010 and GP2013.

UPDATE UPR00500 SET TXSHANTY = 0 WHERE SFRFEDTX + SHFRFICA + SHFRSTTX + SFRLCLTX = 0 UPDATE UPR00500 SET TXSHANTY = 1 WHERE SFRFEDTX + SHFRFICA + SHFRSTTX + SFRLCLTX > 0 UPDATE UPR00600 SET TAXABLE = 0 WHERE SBJTFDTX + SBJTSSEC + SBJTMCAR + SBJTSTTX + SBJTLTAX + SBJTFUTA + SBJTSUTA = 0 UPDATE UPR00600 SET TAXABLE = 1 WHERE SBJTFDTX + SBJTSSEC + SBJTMCAR + SBJTSTTX + SBJTLTAX + SBJTFUTA + SBJTSUTA > 0

To learn more about Microsoft Dynamics GP and other business solutions offered by InterDyn BMI click here or contact us.