Dynamics GP

Posts tagged with Dynamics GP

Management Reporter: "The given key was not present in the dictionary"

A recent error I received when attempting to export a Management Reporter report to Excel was the following:

"The given key was not present in the dictionary"

After several attempts I found that by eliminating one or both of the following situations resolved the error.

1) By unmarking the option "Export to a single worksheet", I was able to export to Excel.

2) It appears the error also appeared when I had a value in the report footer. When I deleted the value in the footer I was able to export the report to Excel.

As mentioned, the error occurred when both situations were present or just one.

Cannot create ScribeInternal database

The Insight application installed without any issues. However, the ScribeInternal database could not be created after several attempts. We tried creating the database manually, assigning the sa user to the db_owner role, and then updating the existing db using the internaldb.exe.

Browsing the server, we noticed the SQL Server master database were owned by a 'not sa' user. Running the sp_changedbowner procedure only returned an error, and even Microsoft support was at a loss to explain how this had happened or how to change it.

We installed a new SQL instance on the same server and verified sa was the owner of all the master databases. On this instance, we were able to create the ScribeInternal database successfully.

Is Payroll Processing Required to Add Employees to Work Centers in GP Manufacturing?

When setting up work centers in GP Manufacturing it is possible to add employees to a work center and calculate labor according to employee pay rates, even if you don't own the Payroll Processing module.

Employee and Pay Code master records are available as a standard part of GP, and can be linked to work centers.

To assign an employee to a work center:

1. Create the Employee ID in the Employee Maintenance Window. (HR & Payroll >> Cards >> Payroll >> Employee)

2. In the Work Center setup, add the Employee ID and subsequent details for that work center.

You can also calculate labor in WIP according to specific Employee's pay rate, rather than using the standard labor cost. The steps for this are outlined at http://njevity.com/blog/calculate-specific-employee-labor-rates-gp-manuf....

Calculate Specific Employee Labor Rates in GP Manufacturing Without Payroll Processing

Payroll Processing is not required in order for Microsoft Dynamics GP Manufacturing to calculate labor according to specific employee pay rates.

For WIP to use an employee's pay rate, the WIP settings need to be correct. In addition, the Pay Code needs to be linked to the Labor Code of the routing sequence, and the Pay Code must also be linked to the Employee ID.

Complete the following steps:

1. Make sure that in WIP setup, the box next to "Always Use Standard Labor Rate" is NOT checked. (Manufacturing >> Setup >> System Defaults >> WIP)

2. Set Up the appropriate Pay Codes (HR & Payroll >> Setup >> Payroll >> Pay Code)

3. Create the Employee ID in the Employee Maintenance Window. (HR & Payroll >> Cards >> Payroll >> Employee)

4. Link the Pay Code to the Employee ID - In the Employee Pay Code Maintenance window, select the Pay Code and complete the information, including the employee's pay rate. (HR & Payroll >> Cards >> Payroll >> Pay Code)

5. Link the Pay Code to the Labor Code - In the Labor Code Definition window, enter the associated Pay Code in one of the available fields Pay Code fields. (Manufacturing >> Cards >> Labor Codes)

Management Reporter: Dynamic Forecast (Conditional Columns)

By using the Conditional Print Control available in the Management Reporter column layout a user can easily create a forecast incorporating both Actual and Budgeted amounts.

For example, let's assume we have a 12 month calendar fiscal year. Create a column layout with 26 columns. The first column would be for the row description and the last column would be a Total. There would then be 2 columns for each period of our fiscal year. Each period would have a column for Actual and another column denoting Budgeted amounts. So, Column B would be Period 1 Actual and Column C would be Period 1 Budget. Column E would be Period 2 Actual and Column E would be Period 2 Budget...and so on.

We now want to Conditionally hide columns based on report date (base period). For each PERIODIC column with ACTUAL, put "P<=B" in the Print Control row. For each PERIODIC column with BUDGET, put "P>B". By doing this, actuals will show in columns where the Period in the column is less than or equal to the report period. Budgets will show in columns where the period is greater than the report period.

For example, if I run my report as of 4/30/2014, actual amounts will show in my Period 1 thru 4 columns and budget amounts will show in Period 5-12. The total column will then add these amounts creating a forecast total.

This is a great way to build your layout one time and have the actual and budget amounts populate solely based on the report date.

Syndicate content