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

Maps will not display in Dynamics CRM 2013 forms

One of the exciting new features about Microsoft Dynamics CRM 2013 is that it now offers Bing maps inside of various entity records like Accounts, Contacts, Leads, and Opportunities. In a recent upgrade from CRM 2011 to 2013 we noticed that the Bing maps functionality was missing from these forms. This is because you need to Activate the proper forms within the entities that you would like Bing Maps to show.

To Activate these forms in Dynamics CRM 2013 navigate to Settings >> Customizations >> Customize the System.

1. Expand the list of "Entities" and expand the Entity in which you want to Activate the form (Clicking the small arrow to the left will expand).
2. Select "Forms".
3. Select the form where the Name equals the entity you are in (if you are in Account, select Account form).
4. Click Activate on the top of the toolbar of the forms window. (Make sure this is the only "Main" form type that is activated. If the Information main form type is also activated you will need to select this and click Deactivate.)

You will need to perform these steps for each entity that you want Bing maps to show on.

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.

Creating a new security role in Microsoft Dynamics CRM (Best Practices)

It is helpful to create new security roles in Microsoft Dynamics CRM to control access for users. For example, you want a user to have the ability only to see records that they own, or perhaps you do not want your users to be able to delete any existing CRM records -- creating a new security role can provide these restrictions.

To create a new security role in CRM, navigate to the Settings tab >> Administration >> Security Roles. There is a default baked-in set of standard security roles provided by Microsoft. If you open one of these up you will notice that you can not edit these. In order to create a new security role there are two ways to do so:

1. Click the New button at the top of the list.
2. Copy an existing security role, rename, and modify to your liking.

It is a best practice to go the route of Option 2 as it is far easier to whittle away the permissions you do not want the role to have than to build a role from scratch. (Unless you have experienced the thrill of banging your head against the wall whilst creating a new security role from scratch, it may not be outwardly obvious that this can lead to the fool's task of an Easter-egg hunt for assigning necessary permissions.) An exception where you may want to create a New security role from scratch is if the role will only contain a few "add-on" permissions (take the example above where the majority of your users will not be able to delete records, however you want to create a simple role where the delete privilege is allowed for say Accounts and Contacts).

This leads into the concept offered by Microsoft called "layering". A user can be assigned multiple security roles giving that user as much access as the highest level of security they are assigned to. If we refer to my examples up top, if a user is assigned to the role that does not permit them to delete any existing CRM records but also to the new role you created that allows them to delete Accounts and Contacts, they will be able to delete Accounts and Contacts despite being assigned both roles.

Syndicate content