The scenario is that you're setting up the new Workflow 2.0 functionality in Microsoft Dynamics GP 2013 R2, whether it be a Purchase Order Approval, Purchase Requisition Approval, Payroll Timecard Approval or Project Timesheet Approval workflow type.

In the workflow step window, when you attempt to select a user as an approver / Assign To, the Workflow User Setup window shows with the following options:

Selection Type:

A. People and Groups

B. Hierarchy

C. Workflow Role

What exactly do these selection types mean/offer?

In this blog, we'll start with the easiest of the options: People and Groups

With this option, you can use it to browse your Active Directory users and groups, to select to be the approver for the specific step in the workflow.

In the 'Find' field, you'll enter a Windows user or group that you have setup in Active Directory, then click the magnifying glass/check button which will verify that the user or group selected exists in the Active Directory.

Once you've selected the user or group you want as the workflow approver and verified it, you can then click the 'Add' button which will add it as that workflow's approver.

In this example, I'm on the CONTOSO domain and I have a USER_A user account setup in my Active Directory that I want to make the approver for the Purchase Requisition Approval workflow step 1 that I have setup.

In the Workflow Maintenance window, on this step's window, I click the lookup button next to the 'Assign to:' field, which opens the Workflow User Selection window as mentioned.

In the Workflow User Selection window, I choose 'People and Groups' for the Selection Type field, then in the 'Find' field, I enter my USER_A user account and click the verify button, which pulls the domain\userid for that user account from the Active Directory.

When I click the 'Add' button, it will add this user account to the 'Selected Users' field.

Once I have my selected user account that I want to make the approver for the workflow step, I then click the OK button which will add this user account as the approver, in the workflow step window.

Once this is completed, in this example, since I have the condition that 'Action is always required for this step', and this is the first step in the Purchase Requisition Approval workflow, each time a requisition is submitted from the Purchase Requisition Entry window, it will be assigned to USER_A for approval.

As it shows in the bottom right-hand corner of the Workflow Maintenance's step window, you can add multiple users and/or groups as approvers for a step, then use the options under 'Completion Policy' for:

--Only one response needed

--Majority must approve

--All must approve

In parts 2 and 3 of this Workflow User Setup window options blog series, I'll also be going through the other two selection types of 'Hierarchy' and 'Workflow Roles'.

Hopefully these blogs will help make sense of the options that are presented to you in the new Workflow 2.0 functionality when setting up approvers for workflow types.

We're continuing with the Workflow User Setup window used to assign approvers in the new Workflow 2.0 feature found in Microsoft Dynamics GP 2013 R2.

In part 1 of this blog series, we talked about the selection type of 'People and Groups'.

In this blog, we're still using the same scenario of setting up the new Workflow 2.0 functionality in Microsoft Dynamics GP 2013 R2, whether it be a Purchase Order Approval, Purchase Requisition Approval, Payroll Timecard Approval or Project Timesheet Approval workflow type.

For this example, we're using the Purchase Requisition Approval workflow type, with a domain name of 'CONTOSO' and Active Directory users: CONTOSO\USER_A, CONTOSO\USER_B, CONTOSO\USER_C, and CONTOSO\USER_D.  

To select an approver for this first step of the Purchase Requisition Approval workflow, we click on the lookup/magnifying glass button next to the 'Assign To' field, which opens the Workflow User Setup window.

In the Workflow User Setup window, for the 'Selection Type' field, we now choose the 'Hierarchy' option, which then enables a 'Start From' and 'Assign To' field as well.

How the Hierarchy selection type works is, when a batch or document is submitted for approval through Workflow 2.0, to find the approver to which it'll assign to, it will first look at the 'Start From' field to find out what is listed there, then once the functionality finds that, it will then look at the 'Assign To' field to find what is selected there. By using the two values, Workflow 2.0 will know where to assign the batch or document to, for approval, for this first step.

Each step in a specific workflow type can be setup with different approvers and selections in this window, for example, while we're using Hierarchy for step 1, we may be using People and Groups for step 2 and so on.

For the 'Start From' field, there are the following options:

>>Workflow originator - this option means that when a batch or document is submitted through Workflow for approval, when it looks to find what approver to assign it to, it will start with the Windows user account that the user was logged onto the machine as, while they were accessing Dynamics GP 2013 R2, and created/submitted the batch or document for approval.

***NOTE: In order to have the Windows account that we're logged onto the system on while submitting a requisition for approval, (The Workflow Originator), be the approver for that same requisition, in the Workflow Maintenance window, we must have the 'Allow originator to be an approver' option marked, otherwise instead of making the Workflow Originator the approver, it will default to the manager of the overall Workflow type, in this case Purchase Requisition Approval.

     This is true regardless of which Workflow role is selected, and in any case where the user account submitting the document or batch for approval is also going to be the approver of those same documents/batches.

>>Workflow manager - this option means that when a batch or document is submitted through Workflow for approval, when it looks to find what approver to assign it to, it will start with the specified manager for the workflow type being used. In our example, for the Purchase Requisition Approval type, we would click on the 'Purchase Requisition Approval' in the Workflow Maintenance window, to see the manager selected. Here you can see we have USER_D as the manager of the Purchase Requisition Approval workflow type.

>>Alternate final approver - When you choose to create a new workflow, in this case for Purchase Requisition Approval, a window will open where you can enter the name of the workflow, select options and what to do when a task is overdue, as well as activate the workflow. Under the list of 'Options' on this window is an option to 'Use alternate final approver', which uses the same Workflow User Setup window we're discussing. If you have a Windows user account listed in this field, you can select this option to have the workflow start with, when attempting to find the approver to send the document or batch to. In this screenshot, I have USER_D selected for my alternate final approver, for the Purchase Requisition Approval workflow I have setup.

>>Requested by - After setting up and activating the Purchase Requisition Approval workflow type, requisitions are then created and submitted for approval via the Purchase Requisition Entry window (Transactions > Purchasing > Purchase Requisitions). In this window, on the header part at the top, there is a 'Requested By' field as well as another 'Requested By' field in the Line section of the window, which is considered the Line Requested By. Because this field is populated by the GP account you're logged into Microsoft Dynamics GP 2013 R2 as, the application again will look at the Windows user account you're logged onto the machine as, then go into Active Directory and find the Direct Manager, Skip Level Manager or Number of Levels manager accordingly.

>>Line requested by - This option is the same as the 'Requested By' option.

>>Lastly, when using either the 'Project Timesheet Approval' or 'Payroll Timecard Approval' workflow types, there is also an option to use 'Employee' under the Hierarchy selection in the 'Start From' field and also under the Workflow Role selection, as the role. With this option, you can set the project timesheet or payroll timecard to be sent to the employee's direct manager, skip-level manager or use the number of levels to skip multiple managers to get to a specific manager for approval. Using 'Employee' for the Workflow Role would send the timesheet/timecard to the actual Employee/Windows user account for approval, again granted that the option to allow the originator to be the approver is marked, otherwise it'll default to the employee's manager.

***NOTE: We currently have a known issue with the 'Payroll Timecard Approval' and Project 'Timesheet Approval' types in Workflow 2.0, where the issue is when specifying the approver for a workflow step and choosing the Employee's direct manager, this is not working correctly. What we're seeing is that these workflows default back to the manager of the workflow itself, as listed in the Workflow Maintenance window.  The current work-around is, as long as users are submitting their own timecards, the approver should be changed to use 'Workflow Originator' / 'Direct Manager', by using this, the workflow will look at the Windows user account being used, then look in Active Directory for that user's actual manager to assign the timecard or timesheet to for approval.

Let's take a look at an example of how the 'Hierarchy' selection type for approver works in Workflow 2.0. For an example, let's say we have the following setup in Active Directory:

User_A, who's manager is setup to be User_B

User_B, who's manager is setup to be User_C

User_C, who's manager is setup to be User_D

While logged into Windows as User_A, we're going to create and submit a requisition through Dynamics GP 2013 R2 / Workflow 2.0.

For the approver, we're going to setup the Workflow User Setup window to use 'Hierarchy' for the Selection Type, 'Workflow Originator' for the Start From value and then 'Direct Manager' for the Assign To value.

With this setup, since User_A will be considered the creator or originator of the submitted requisition, the requisition will be assigned to User_A's direct manager for approval, which is User_B, as per Active Directory.

If 'Skip Level Manager' was setup for the Assign To value, then it would've skipped User_A's manager and gone onto that manager's manager, which is User_C.

Lastly, if 'Number of Levels' was chosen as the Assign To value, and we chose '3' for the number of levels, approval of the requisition would be assigned to the third level of manager, which in our example, would be User_D.

The Assign To values of 'Direct Manager', 'Skip Level Manager' and 'Number of Levels', work the same regardless of what is selected for the Start From value, as long as Hierarchy is chosen for the Selection Type.

This covers the Windows User Setup window and using 'Hierarchy' for the Start From value. The next and last of the three blogs regarding this window will be on using 'Workflow Role' for the Start From value.

This is the last of the three blogs covering the Workflow User Setup window used to assign approvers in the new Workflow 2.0 feature found in Microsoft Dynamics GP 2013 R2.

The other two blogs can be found here:

--Workflow 2.0's Workflow User Setup window options: part 1: People and Groups

--Workflow 2.0's Workflow User Setup window options: part 2: Hierarchy

We're still using the same scenario of setting up the new Workflow 2.0 functionality in Microsoft Dynamics GP 2013 R2, whether it be a Purchase Order Approval, Purchase Requisition Approval, Payroll Timecard Approval or Project Timesheet Approval workflow type.

For this example, we're using the Purchase Requisition Approval workflow type, with a domain name of 'CONTOSO' and Active Directory users: CONTOSO\USER_A, CONTOSO\USER_B, CONTOSO\USER_C, and CONTOSO\USER_D.  

To select an approver for this first step of the Purchase Requisition Approval workflow, we click on the lookup/magnifying glass button next to the 'Assign To' field, which opens the Workflow User Setup window.

In the Workflow User Setup window, for the 'Selection Type' field, this time, we're choosing the 'Workflow Role' option, which then enables a 'Workflow Role' field as well.

When we're using the Workflow Role option for Selection Type, we're telling Workflow 2.0 that we want the approver of the submitted documents and batches to be that Windows user account that is currently assigned to that position or role.

The options we have for Workflow Roles are the following:

>>Workflow Originator - When this role is selected as the approver, and in this case, a requisition is created and submitted for approval, the requisition is then assigned to the Windows user account that the user is logged on the machine as, while in Microsoft Dynamics GP 2013 R2, creating and submitting the requisition for approval through the Purchase Requisition Entry window. (Transactions > Purchasing > Purchase Requisition).

>>Workflow Manager - When this role is selected as the approver, in this case, a requisition created and submitted for approval, the requisition is then assigned to the listed manager in Active Directory, for the Windows User account the user is logged on the machine as, as listed in Active Directory,  while in Microsoft Dynamics GP 2013 R2, creating and submitting the requisition for approval through the Purchase Requisition Entry window. 

>>Alternate Final Approver - When this role is selected as the approver, in this case, a requisition created and submitted for approval, the requisition is then assigned to the Windows user account selected as the 'Use alternate final approver' in the Workflow Maintenance window. In this example, I have USER_D listed as the alternate final approver, so the requisition will be assigned to this user for approval.

>>Requested By - After setting up and activating the Purchase Requisition Approval workflow type, requisitions are then created and submitted for approval via the Purchase Requisition Entry window (Transactions > Purchasing > Purchase Requisitions. In this window, on the header part at the top, there is a 'Requested By' field as well as another 'Requested By' field in the Line section of the window, which is considered the Line Requested By. Because this field is populated by the GP account you're logged into Microsoft Dynamics GP 2013 R2 as, Workflow 2.0 will look at the Windows user account the user is logged on as, and make that user account the approver.

>>Line Requested By - This option works the same as the 'Requested By' option.

An example of how this all works is, for an example, let's say we have the following setup in Active Directory:

User_A, who's manager is setup to be User_B

User_B, who's manager is setup to be User_C

User_C, who's manager is setup to be User_D

While logged into Windows as User_A, we're going to create and submit a requisition through Dynamics GP 2013 R2 / Workflow 2.0 for approval.

For the approver, we're going to setup the Workflow User Setup window to use 'Workflow Role' for the Selection Type, then select 'Workflow Originator' for the Workflow Role. When we submit a requisition for approval, the system will look at the Windows user account that we're currently logged onto the machine as, while running Microsoft Dynamics GP 2013 and attempt to assign the requisition to it for approval. In this case, User_A.

***NOTE: In order to have the Windows account that we're logged onto the system on while submitting a requisition for approval, (The Workflow Originator), be the approver for that same requisition, in the Workflow Maintenance window, we must have the 'Allow originator to be an approver' option marked, otherwise instead of making the Workflow Originator the approver, it will default to the manager of the overall Workflow type, in this case Purchase Requisition Approval.

     This is true regardless of which Workflow role is selected, and in any case where the user account submitting the document or batch for approval is also going to be the approver of those same documents/batches.

So, with the 'Allow originator to be an approver' option marked, if we have 'Workflow Originator' selected, the submitted requisitions will be assigned to the Windows user account the user is logged onto the machine as, while logged into Microsoft Dynamics GP 2013 R2 submitting the requisition.

If we choose 'Workflow Manager' for the role, any submitted requisitions will be assigned to the manager of the Purchase Requisition Approval workflow type, which in this example would be the USER_D Windows account.

If we choose Alternate Final Approver' for the role, any submitted requisitions will be assigned to the Windows account we have setup as the 'Use alternate final approver' field, in Workflow Maintenance window:

If we choose 'Requested By' or 'Line Requested By' for the role, any submitted requisitions will be assigned to the Windows user account that is logged onto the machine while using Microsoft Dynamics GP 2013 R2 and, in this case, Purchase Requisition Approval workflow to submit requisitions for approval. Because the 'Requested By' fields in the Purchase Requisitions window both populate with the GP user, not the Windows user, so there's no Active Directory to pull the GP user from, it instead looks at the Windows user account the user is logged on as when submitting the requisition instead and will use that user, again, depending on whether or not the 'Allow originator to be an approver' option is marked or not.

Additional Notes:

--If, for any reasons, Workflow 2.0 cannot verify a Window user account's direct manager in Active Directory or the user doesn't have one designated, the application will default to the Windows user account itself, not its manager.

--If, for any reasons, Workflow 2.0 cannot verify a Windows account in Active Directory, it will default to the overall Workflow type manager as designated in the Workflow Maintenance window.

Hopefully these blogs have addressed many of the questions you may have in setting up the new Workflow 2.0 functionality available in Microsoft Dynamics GP 2013 R2. I feel once you understand the information in these three blogs regarding how to correctly setup the approvers you want to have, you'll have a pretty good grasp on setting up the new workflows. 

Good Luck!!

We’ve been seeing some cases coming in revolving around the new Requisition Manager features in GP 2013 R2, so we wanted to get some of this information out there for everyone!

Problem: I can’t see any requisitions, except for ones that I’ve submitted! I’m assigned as the approver, but I can’t see it in the lookup.

Solution: You need to set up the user to be allowed to see all requisitions displayed. Go to Tools >> Setup >> Purchasing >> Purchase Order Processing >> Requisition, and look for the “Display Requisitions During Entry For:” section, and check the box for “All Requisitions” by the user that you want to grant the access to. Once this is done, re-enter the requisition, and it should now show up for the approver!

Problem: Approval emails aren’t being generated! I can submit, but the approver isn’t receiving an email.

Solution: You need to make sure that you’ve set up the email settings properly under Tools >> Setup >> System >> Workflow Setup. Check the box to “Enable Email for Workflow,” and enter your outgoing SMTP settings. Work with your system administrator if you don’t know what is supposed to be entered here. The Test E-Mail button is your friend!

Problem: Great! Now the emails are sending, but I can’t click to Approve in the email! Clicking the link brings up a page in Internet Explorer that just says “Page Cannot be Displayed.”

Solution: GP Web Services needs to be installed for this to work! In the same Workflow Setup window we had open previously, make sure you’ve typed the name of the server where GP Web Services is installed properly, and that the port is correct. You shouldn’t need to enter the FQDN, just use the NETBIOS name of the machine where Web Services is. Again, the “Test Email Action” button is your friend! Do not check the SSL box, unless you’re actually using SSL! The “Approve” and “Reject” functions are simply embedded links to Web Services, and they are generated using what is in this field. If you check to enable SSL, but you’re not using SSL, you won’t be able to complete the action because the address will contain an extra “s” after “http.”

Problem: When I click the link in the email to view the document, the window opens, and I can view the requisition, but I don’t see the “Approve” or “Reject” buttons!

Solution: The document lookup link in the email is a drill back that opens up the “Inquiry” window. You can’t take action on a requisition from the Inquiry window. You have to use the “Entry” window. This behavior is by design, for licensing and permissions purposes.

Hopefully these tips will help you get started! Stay tuned for more updates from the support teams here!

We recently ran into an issue in Workflow 2.0 where you will see a status very similar (the date is the exceptions) to the one in the screen shot below. We have identified that this issue is caused when your Fully Qualified Domain Name (FQDN) differs from the NetBIOS name in your environment. The reason you are seeing this status is because Workflow 2.0 uses your FQDN when determining the approver of a Workflow, but you are actually logging in using the Windows NetBIOS name. Please see the example below for further explanation.

EXAMPLE:

Your FQDN = yourdomain.com

Your NetBIOs = domain.com

You can see how you are logged into Windows by using the whoami command at the command prompt. You will see that you are logged in as domain\<userid> (NetBIOS name), which is where the problem lies in this domain environment. GP looks to Windows for the credentials to use to determine the approver of the Workflow. It sees that you are logged in as domain\<userid>. In the backend the database has a record written in the WFI10004 table that is looking for yourdomain.com\<userid> in the WorkflowTaskAssignedTo column. Therefore Workflow does not know who the approver is so it leaves the name blank.

We are looking to resolve this issue in a later release of GP. Unfortunately I’m unable to tell you which one it will be at this time. Please be sure to refer to the release notes for Dynamics GP to see when the issue has been addressed. In the meantime, there is a workaround which you will see below.

WORKAROUND:

Run the update script below against the WFI10004 table in the Company database where you are experiencing the issue. After you run the update statement, you should be able to go into the document and see the person that is supposed to approve the Workflow. You will have to run the statement each time a Workflow is submitted.

UPDATE WFI10004 SET WorkflowTaskAssignedTo = 'NetBIOS Name\<userid>' WHERE DEX_ROW_ID = '<DexRowID>'

NetBIOS Name           = In the example above this would be domain

Userid                         = The Windows User ID of the Approver

DexRowID                  = References the column in the WFI10004 table called DEX_ROW_ID

Below is a screenshot of what the status should look like. In this case, my approver’s User ID is WC.

NOTE:

If you are setting up a test environment and you have a local user originating a Workflow and the approver is a domain user, you will also see the same issue.   You need to be sure that all Workflow users are in Active Directory.

Hopefully this will help you understand why you are seeing this status and what you can to prevent it until the fix is released.

This article explains how you can integrate Asset Book ITC information into an Asset Book record using the Fixed Assets Import/Export functionality inside Microsoft Dynamics GP.

Data in the Asset Book ITC window include Section 179 amounts, TEFRA, and ITC amounts:

The data entered in this window could affect the Cost Basis on the Asset Book window and if the Cost Basis is changed, this is a depreciation sensitive field, and you will be asked to “recalculate” depreciation.

This information is possible to integrate into Fixed Assets using the Fixed Assets Import/Export functionality inside of Dynamics GP, however, there are a few things that you need to know when bringing this information in.

1. If the ITC Cost information causes the Cost Basis amount on the Asset Book window to change, this is a Depreciation sensitive field and you will be asked to Reset Year, Reset Life or Recalculate.
2. An import cannot handle this “recalculate” message because it doesn’t have the capability to choose 1 of the 3 options.

To avoid running into this message and to have a successful import of an Asset Book and Asset Book ITC information you will want to follow these recommendations.

A. The Cost Basis on the Asset Book record will need to be the Cost Basis when taking into consideration the amounts in the Asset Book ITC window.

For example, if an Asset Book record is being integrated with the following Asset Book ITC information:

B. The Asset Book record associated with the information above must be imported using a $700.00 Cost Basis.

This is because with a 'Sec. 179 Exp. Ded. amount' of $500.00 the asset’s Net Cost Basis is now $700.00. The Net Cost Basis from the Asset Book ITC window becomes the Asset Book’s Cost Basis and if these are different you will be required to reset year, reset life or recalculate.  By integrating the Asset Book with a Cost Basis of $700.00 you bypass the recalculation of depreciation message.

NOTE: The functionality of integrating Fixed Assets with eConnect and Integration Manager currently does not allow for integrating Asset Book ITC cost information, although it is an option to integrate. This functionality is currently being reviewed.

We’ve recently come across a few cases involving our new Identity Management features in Microsoft Dynamics GP 2013 R2. As you may know, the new features all you to link a set of Windows Credentials to a GP credential. Doing this enables you to log into the Web Client using only your Windows credentials, and the link will log you directly into GP automatically.

In the back end, the actual SQL login takes place by a Web Client Proxy user. During installation, you are prompted for a username and password for this user. If for some reason, you need to change or reset the proxy account’s password, you can do so by following these steps:

1. Launch GP Utilities, click through to the Additional Tasks window.

2. Select “Manage Web Client SQL Server login,” and click Process.

3. Enter the Login Name, and then the Password twice.

4. If you’re changing the password, check the box.

5. Click Save, then close Utilities.

**IMPORTANT**

After doing this, you must run a repair on Dynamics GP Web Client, or else the automatic login will stop working. The credentials are encrypted and cached locally in the installation directory, and the local credentials won’t be updated until you run the repair.

After running a repair, you will be able to automatically log into GP using just your Windows Credentials again.

Another issue that has come up occasionally is a 401.1 authentication error when logging into Web Management Console (WMC) on the same server that it is installed on. If you hit WMC from anywhere else in the environment, it works fine. Upon hitting the site directly from the server, you will be prompted for credentials three times, and then you will get a 401.1 error.

We are currently still investigating the cause for this issue, but in the meantime we have found that making the following registry tweak will resolve the issue. See the KB referenced below for more information.

1. Open up a new Notepad document, and paste in the following text:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]

"DisableLoopbackCheck"=dword:00000001

1. Save the .txt file to your desktop.

2. Change the file extension to .reg instead of .txt.

3. If you can’t see the file extensions, you’ll need to disable the “Hide Extensions” option in Windows Explorer.

   1. http://windows.microsoft.com/en-us/windows/show-hide-file-name-extensions#show-hide-file-name-extensions=windows-7

4. Run an IISRESET, and then attempt to log into WMC again.

To set the value back to what it was previously, you can change the DWORD value from 00000001 to 00000000.

(This workaround involves making a change to the System Registry. If you are not comfortable making changes, consult with your system Administrator before making any changes, and make sure that you have a full disaster recovery solution in place before modifying the Registry. Make this change at your own risk!)

Dan Peltier

A question that we often get asked in support is: “Should I enable Multicurrency even if I’m not going to use different currencies?”

This is completely up to you as a customer, but based on many support incidents our recommendation would be yes, enable Multicurrency. But why enable it?  There are a few reasons:

1) If you enable Multicurrency and set a Functional Currency initially this will prevent you from having to run a lengthy Check Links process later on down the road if you decide to enable Multicurrency.  If you don’t enable Multicurrency and decide 10 years later to enable it, you will be required to run the Check Links process to assign all your transactions to your Functional Currency, this could take quite some time depending on the amount of data that you have.

2) If you are using Analytical Accounting and printing reports using Management Reporter, Management Reporter relies heavily on the Currency ID associated with the transactions in General Ledger and in Analytical Accounting. If these Currency ID’s don’t match Management Reporter will not pull the unmatched transactions onto the report. By enabling Multicurrency you an ensuring all Analytical Accounting and General Ledger data has a Currency ID leaving less room for discrepancies.

3) Mismatched currency ID's may also result in documents not showing up when trying to use apply windows in Payables Management, Receivables Management or Lockbox. Therefore, if you do not wish to use Multicurrency, it is still recommended to leave Multicurrency Management marked in the Registration window going forward once you set up a functional currency, and grant access to only this one currency ID going forward.

4) You may want to use different currencies in the future and this will provide that functionality, but you do not have to use this functionality until you are ready.

5) Many Third Party Applications and Integrating Applications require a Functional Currency. When you enable Multicurrency all your transactions will be associated with your main Functional Currency and will remain going forward. It's important to make sure your Functional Currency is correct before selecting it.  Your Functional Currency should be the primary currency in which your company uses for its financial records. 

NOTE: Once a Functional Currency has been selected this cannot be changed.

6) Multicurrency Management is now an included with your registration keys in Microsoft Dynamics GP 2013.

There are some helpful Knowledgebase Articles that will help with setting up your System and Company for Multicurrency:

System setup checklist for Multicurrency Management in Microsoft Dynamics GP
 

http://support.microsoft.com/kb/858556

 How to set up a company in Multicurrency Management in Microsoft Dynamics GP

http://support.microsoft.com/kb/858730

NOTE: If you aren’t using multiple currencies some of this setup will not be required.

The steps below can be used as a guide to change your Web Services address from http to https.  We do not support all of these steps within Microsoft Dynamics GP Support because every environment is different and the needs of every environment may vary.

***NOTE: Once Web Services is changed to use the HTTPS address, you will not be able to make any changes to the policy nodes within the Dynamics Security Console. Any changes to the policy nodes must be done while Web Services is still using the default HTTP address. Changes made to the policy nodes while in HTTP, will be reflected and usable while Web Services is using HTTP addresses.

1. Pick a new port to be the SSL port.

a. Only requirement is that it be unused.

2. Create (or acquire) the SSL certificate.

3. Register the certificate for the new port (using netsh or httpcfg)

a. NETSH: netsh http add sslcert ipport=0.0.0.0:<PORT> certhash=<THUMBPRINT ID> appid=<ARBITRARY GUID>

b. EXAMPLE: netsh http add sslcert ipport=0.0.0.0:48622 certhash=05a298da9200ee2e18250452e07928ce8f716f27 appid={07663267-F6A1-4F6F-9833-56FD0ABE0B89}

4. Update the wsHttpBinding in WSBindings.config (C:\Program Files\Microsoft Dynamics\GPWebServices\ServiceConfigs)

a. Copy the existing binding configuration and paste it in the same section

b. Change the security of this one from ‘Message’ to ‘Transport’

c. Change the name of this configuration as well (anything unique will do)

Example:

<wsHttpBinding>

<binding name="WSHttpBindingTarget" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true">

      <security mode="Message">

       <message clientCredentialType="Windows"/>

     </security>

   </binding>

<binding name="WSHttpBindingTargetSSL" maxBufferPoolSize="2147483647" maxReceivedMessageSize="2147483647" messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true">

     <security mode="Transport">

       <message clientCredentialType="Windows"/>

     </security>

   </binding>

</wsHttpBinding>

5. Update the service config section (DynamicsGP.config or DynamicsGPLegacy.config)

a. Update the GP native service to point to your binding configuration (new name

b. ADD a new base address that uses https://MACHINE:[NEW_PORT]

i. Leave the original in place for metadata support                  

Example:

   <baseAddresses>

           <add baseAddress="http://<machinename>:<assignedport#>/Dynamics/GPService"/>

           <add baseAddress="https://<machinename>:<SSLPort#>/Dynamics/GPService"/>

         </baseAddresses>

*NOTE: Replace <machinename> with Server name and <SSLPort#> with new port from step 1.

c. Change behavior to point to the ‘dynamic’ rather than ‘static’ behavior (these are defined at the bottom of the same file).

i. This is required to successfully add service references to the new endpoint

Example:

<service name="Microsoft.Dynamics.GP.WebServices.Contract.DynamicsGP" behaviorConfiguration="GPDynamicMetadataBehavior">

       <endpoint address="Mex" name="http" binding="customBinding" bindingConfiguration="CustomBinding" contract="IMetadataExchange"/>

       <endpoint address="GPService" name="GPWebService" binding="wsHttpBinding" bindingConfiguration="WSHttpBindingTarget" contract="Microsoft.Dynamics.GP.WebServices.Contract.IGPServices"/>

6. Update firewall configuration

a. Make sure your new port is allowed

b. Can simply add this port to the existing GPService rule

i. Start -> Control Panel -> Administrative Tools -> Windows Firewall and Advanced Security

ii. Click on Inbound Rules

iii. Double click on GP Service

iv. Select the Protocols and Ports tab

v. Insert a comma and your new SSL port in the port field of local ports

7. Add URL reservation

a. NETSH: netsh http add urlacl url=https://+:<SSLPort#>/ user=<SERVICE USER>

NOTE: TRAILING SLASH IS REQUIRED!

8. Service should start successfully

The following error is encountered on Microsoft Dynamics GP 2013 R2 when attempting to select Database Disabler in Professional Services Tools Library (PSTL): “You are not registered for the selected utility.”

If you run into an issue in which you disabled a database using Database Disabler on a previous version/build of Microsoft Dynamics GP and you are now attempting to enable the Database on Microsoft Dynamics GP 2013 R2, you can run the following scripts to re-enable the database since you won't be able to do so using Database Disabler in the Professional Services Tools Library.

** As always, ensure that you have a valid back-up of your DYNAMICS database before proceeding.**

1. Run the following statement and make note of the cmpanyid that is referenced for that company:

Select * from DYNAMICS..SY01500

2. You will then modify the script below and replace xx for the cmpanyid with the actual cmpanyid that was listed in the script results in Step 1 (above) for the cmpanyid of the database that you want to re-enable.

USE [DYNAMICS]

GO

INSERT INTO [dbo].[SY60100]

                ([TRKUSER]

                ,[USERID]

                ,[CMPANYID]

                ,[SRBCHSEC_1]

                ,[SRBCHSEC_2]

                ,[SRBCHSEC_3]

                ,[SRBCHSEC_4]

                ,[SRBCHSEC_5]

                ,[SRBCHSEC_6]

                ,[SRBCHSEC_7]

                ,[SRSFNSEC_1]

                ,[SRSFNSEC_2]

                ,[SRSFNSEC_3]

                ,[SRSFNSEC_4]

                ,[SRSFNSEC_5]

                ,[SRSFNSEC_6]

                ,[SRSFNSEC_7]

                ,[MSCPRMIS])

SELECT [TRKUSER]

                                ,[USERID]

                                ,[CMPANYID]

                                ,[SRBCHSEC_1]

                                ,[SRBCHSEC_2]

                                ,[SRBCHSEC_3]

                                ,[SRBCHSEC_4]

                                ,[SRBCHSEC_5]

                                ,[SRBCHSEC_6]

                                ,[SRBCHSEC_7]

                                ,[SRSFNSEC_1]

                                ,[SRSFNSEC_2]

                                ,[SRSFNSEC_3]

                                ,[SRSFNSEC_4]

                                ,[SRSFNSEC_5]

                                ,[SRSFNSEC_6]

                                ,[SRSFNSEC_7]

                                ,[MSCPRMIS]

                FROM DYNAMICS..[TA60100] where cmpanyid = 'XX'

GO

 3. After you have ran that, you can run the following script to verify that the only record or records present are for the databases that had been disabled but that you re-enabled in Step 2 above.

a. Select * from DYNAMICS..TA0010

4. If this is correct use the following script to remove the record or records.

a. Delete DYNAMICS..TA0010

The database disabler functionality in PSTL has been replaced with the Take Company Offline feature that is now available in Microsoft Dynamics GP 2013 R2. You can get to this by going to GP | Tools | Utilities | System | Take Company Offline. Using this functionality you can take one or more companies offline for maintenance or administrative tasks, such as a year-end close or an update.

Have a great day!
Sarah

Being that the Year-End updates are right around the corner and a lot of customers will be upgrading to newer versions of Dynamics GP such as GP 2013 and GP 2013 R2, we figured this would be a good article to get out to the public to look at.

Many of you have run into this while attempting to run an upgrade of Microsoft Dynamics GP, specifically Dynamics GP 2013, where you're going through the upgrade guide and under the list of 'Known Issues', you see the 'Tables contain incorrect framework information' issue, stating "if the following tables contain incorrect account framework information, the upgrade will fail:

GL10110 - Account Current Summary Master

GL10111 - Account Summary History

GL70500 - General Ledger Report Options

GL70501 - General Ledger Report Options Temporary

GL00100 - Budget Master

GL00201 - Budget Summary Master

To verify this, you run the Account_Framework_Validation script which checks these tables in all company databases it finds listed in the SY01500 system table.

If everything is correct, no records will be returned.

If there are issues with any or all of these tables, this script will tell you exactly what tables, what company database and why it's failing. These issues need to be fixed before the upgrade can be run.

Most commonly, there is a length that is incorrect for specific column(s) in one or more of these tables and that is causing the issue.

For example, if you have an account framework setup for Microsoft Dynamics GP as 5 segments with each segment with a length of 9, then in the GL00100 table, we'd expect to see columns ACTNUMBR_1 through ACTNUMBR_5 for each of the five segments, with these specific columns having a specific length, to correspond with the length of each of these five columns. In this case, these five columns would have a length of 9. If even one of these columns has a different length value, the Account_Framework_Validation script should detect it and it'll need to be fixed prior to the upgrade being run.

**NOTE: For even numbered segment lengths, Dynamics GP will add one to the length in the table columns. For example, we still have 5 segments but this time with lengths of 9, 8, 4, 5 and 6 accordingly. In the GL00100 table, we would still have the ACTNUMBR_1 through ACTNUMBR_5 columns, for the 5 segments, but the lengths would be 9, 9, 5, 5 and 7 accordingly.

The account framework information can be found by running the following scripts against the DYNAMICS or system database:

   --Select * from SY003001

   --Select * from SY00302

The best way to verify the tables that are mentioned by the Account_Framework_Validation script as having an incorrect structure, is to use the 'sp_help' script, such as this, again using GL00100 as an example:

   -- sp_help GL00100

In tables GL00100, GL00201, GL10110 and GL10111, the columns to look at are the ACTNUMBR_# columns.

For tables such as GL70500 and GL70501, the columns to look at are the STACCNUM_# and EDGACNUM_# columns.

Unfortunately, there isn't any way through SQL to manually change these column lengths or number of columns, except for dropping and re-creating the table with the correct structure with data intact. To do this, we recommend using the Professional Services Tools Library, at the version/build of Microsoft Dynamics GP that you're upgrading from, before beginning the upgrade to the new build or version.

The steps are here:

A. On the current version/build of Microsoft Dynamics GP, install the Professional Services Tools Library (PSTL) feature if you don't have it already and add it onto each company database you need to/that have tables failing the account framework validation.

B. In the same GP code folder, find the Dex.ini file and change SYNCHRONIZE=FALSE to be SYNCHRONIZE=TRUE, save changes and close the Dex.ini.

C. Launch Microsoft Dynamics GP Utilities at this same version/build, which will verify the version information and synchronize the account framework. Close out of GP Utilities.

D. Go back into the Dex.ini file and verify the SYNCHRONIZE= line is set back to FALSE. If it isn't, the Microsoft Dynamics GP code is bad and you'll need to re-install it.

E. Have all of the users logged out of the Microsoft Dynamics GP system and databases.

F. Launch the Professional Services Tools Library feature within Microsoft Dynamics GP. In the PSTL window, the 'Toolkit' utility is what you'll want to use.

G. In the Toolkit Options window, choose the 'Recreate SQL Objects' option and click Next.

H. In the System Diagnostics window, select the 'Financial' series and then select a table such as GL00100.

      Still on this window, select the 'Recreate Selected Table' and also the 'Recreate Data for Selected Table(s)' in order to recreate the table with data intact.

I. Click on the 'Perform Selected Maintenance' to proceed. It will show some warning and confirmation boxes you'll need to click through. Once the table is re-created, you'll get a message letting you know that. Click OK.

J. Repeat these steps for each table you need to fix, such as GL00201, etc. If you need to fix a table such as IV70500, you'll need to change the series in step H from 'Financial' to 'Inventory', and so on.
 
K. Once you get the tables re-created to the correct structure with data intact, make backups of them, before running the Account_Framework_Validation script again, to make sure nothing is now returned.

L. Once the Account_Framework_Validation script returns no records at all, indicating these tables are correct structure-wise, make sure you have recent, valid backups of all GP databases and you can begin the upgrade of the databases to the new version and/or build of Microsoft Dynamics GP.

Hopefully this information will answer the other half of the issue, for when records are returned by the Account_Framework_Validation script, and provide information that may allow you to resolve the issue without needing to open a support case. That being said, if you have any questions on the information above or in your own actual Microsoft Dynamics GP environment, we'll be more than happy to assist, as always.

Thank you!!

In GP 2013 R2, you will see one of two error messages (see below) when trying to submit a Workflow after you add an email address to the 'Have Replies Sent to' field in the Message Setup window (GP>>Tools>>Setup>>Company>>Workflow>>Email Messages Setup) using the 'Select Names Options'.

Error 1:

A .Net Framework error occurred during execution of user-defined routing or aggregate 'SendWorkflowAssignmentEmail'. System.FormatException:  The specified e-mail address is currently not supported.

Error 2:

A .Net Framework error occurred during execution of user-defined routine or aaggregate "SendWorkflowAssignmentEmail" System.FormatException: The specified string is not in the form required for an e*/

Workaround:

You can type your actual email address (e.g. example@Microsoft.com) in the 'Have Replies Sent to' field then click the 'Save' button. 

Basically at this time we will want to avoid using the 'Select Names' button/functionality in this field until the issue has been resolved.

GP 2013 R2: Workflow 2.0 - Email Messages Setup Error

Back by popular demand!!   The Microsoft Dynamics GP Team will be creating blog posts this year related to year-end closing processes for Microsoft Dynamics GP.  These articles will include general questions about year-end for that module, and include any changes for year-end that will affect your year-end processes for 2014.  It is recommended to install the 2014 Year End Update.  This will be evident to you as the blogs discuss changes for the year.  Below is the schedule of upcoming blog posts:

November 06, 2014 - GP 2010 Lifecycle and Upgrade Services

November 11, 2014 - Install and Upgrade
November 12, 2014 – Table and Column Changes in Year-End
November 13, 2014 - Payables Management

November 18, 2014 - US Payroll
November 19, 2014 - Affordable Care Act (ACA)
November 20, 2014 - Fixed Assets

November 25, 2014 – Analytical Accounting
November 26, 2014 - General Ledger

December 02, 2014 - Receivables Management
December 04, 2014 - Inventory

December 09, 2014 – Canadian Payroll

*Links to the above blog posts will be added as they are released.  However, we recommend utilizing the Connect section of the Microsoft Dynamics GP Home Page so you get all the latest feeds and information as it is published.  

MORE INFORMATION:

     • Here is a link to the new PowerPoint presentation for "What's New in Year-End 2014" .  (This will be posted at a later date.  Check back for this to be updated.)

     • Here is a link to a comprehensive video presentation for Microsoft Dynamics GP "What's New in Year-End 2014".  (This will be posted at a later date.  Check back for this to be updated.)

     • A link to a PowerPoint presentation for the 'standard' Year-End Close Procedures that generally do not change from year to year. 

     • Below are the direct links to see all the changes included in the update and the downloads to the install once released.

Click HERE for U.S. Payroll Year End Update for Microsoft Dynamics GP 2013
Click HERE for U.S. Payroll Year End Update for Microsoft Dynamics GP 2010

***IMPORTANT NOTES: ***

     • The 2014 Year End Update is currently targeted to release the end of November 2014.  The 2014 Canadian Payroll update is targeted for mid-December.

     • The year end update for Microsoft Dynamics GP 2013 is an all-inclusive update and will include Microsoft Dynamics GP 2013 R2.  

     • The Affordable Care Act changes for calendar year 2015 will be implemented in Microsoft Dynamics GP 2013 and versions going forward.  These changes will not be available for Microsoft Dynamics GP 2010 or prior versions. 

     • This will be the LAST year that a Year-End Update will be available for Microsoft Dynamics GP 2010 so you may want to consider upgrading soon.  Mainstream support (ie. tax updates) will end on 10/13/2015.  Extended support with no updates will end on 10/13/2020. Please refer to the Support Life Cycle for Microsoft Dynamics GP 2010.

I hope this information has been helpful to you.  The Dynamics GP team wishes you a seamless 2014 year-end! 

Thank you!

Cheryl Waswick | Sr. Technical Support Engineer | Microsoft Dynamics GP Applications Support Team

Hello!

Every once in a while we receive Lifecycle questions in regards to different versions of Microsoft Dynamics GP.  This should help to answer some of those questions.

You will see me make reference to Mainstream Support and Extended Support.  Here is a chart that outlines the differences between Mainstream Support and Extended Support.

Microsoft Dynamics GP 10.0:

Microsoft Dynamics GP 10.0 is already in its' extended support lifecycle.  This will be ending on 10/10/2017.


Microsoft Dynamics GP 2010:

Mainstream Support for Microsoft Dynamics GP 2010 will end on 10/13/2015 which means that at that point in time, you will no longer receive tax and year end updates.  Microsoft Dynamics GP 2010 will then move into Extended Support until 10/13/2020.

NOTE: The 2014 U.S. Payroll Year End Update for Microsoft Dynamics GP 2010 WILL NOT contain the Affordable Care Act Changes. For more information on the Affordable Care Act Changes for Microsoft Dynamics GP, please review this blog:
Affordable Care Act changes for Microsoft Dynamics GP
  

Microsoft Dynamics GP 2013:

Mainstream Support for Microsoft Dynamics GP 2013 will end on 4/10/2018 which means that at that point in time, you will no longer receive tax and year end updates.  Microsoft Dynamics GP 2013 will then move into Extended Support until 4/11/2023.

NOTE: The 2014 U.S. Payroll Year End Update for Microsoft Dynamics GP 2013 WILL contain the Affordable Care Act Changes. For more information on the Affordable Care Act Changes for Microsoft Dynamics GP, please review this blog:
Affordable Care Act changes for Microsoft Dynamics GP
  

Extended support for Microsoft Dynamics GP is included in the customers and partners standard support plans.  Here is a link that provided more information as well on the Microsoft Dynamics GP Product Lifecycle:
http://support.microsoft.com/lifecycle/search/default.aspx?sort=PN&alpha=Dynamics+Gp&Filter=FilterNO 
 
With the information provided above, if you are currently on Microsoft Dynamics GP 2010 or earlier, you will want to begin thinking more seriously about upgrading to Microsoft Dynamics GP 2013 or Microsoft Dynamics GP 2015 (when that releases). Upgrade services through Advanced Product Support Services are available for upgrades to a supported version of Microsoft Dynamics GP according to the Microsoft Product Lifecycle Policy. For example, Microsoft Dynamics GP 10.0 to Microsoft Dynamics GP 2013. Customers: If you have any questions regarding upgrade services, please reach out to your Partner to get the ball rolling for a service request. Partners:  You can contact the NA Partner Assist Team at napa@microsoft.com or you can log your own advisory service request at the following location:  MPN - My support benefits and incidents to submit an upgrade service request.

Thank you!
Sarah

The year-end update is a key component to the year-end process. It is very important to ensure the year-end install and upgrade goes as smooth as possible.  Review the install and upgrade tips below to ensure your year-end update installation is successful!

Install and Upgrade Overview

1. The 2014 year-end release is available for Microsoft Dynamics GP 2010 and Microsoft Dynamics GP 2013. 

NOTE: The 2014 U.S. Year End Update for Microsoft Dynamics GP 2010 WILL NOT contain the Affordable Care Act changes. For more information on the Affordable Care Act changes for Microsoft Dynamics GP, please review this blog:
Affordable Care Act changes for Microsoft Dynamics GP

NOTE: The 2014 U.S. Year End Update for Microsoft Dynamics GP 2013 WILL contain the Affordable Care Act changes. For more information on the Affordable Care Act Changes for Microsoft Dynamics GP, please review this blog:
Affordable Care Act changes for Microsoft Dynamics GP

2. Both the Microsoft Dynamics GP 2010 and Microsoft Dynamics GP 2013 releases are MSP files.

3. All MSP files are cumulative. All prior service packs, hotfixes, compliance, and year-end updates are included in the most recent release. For example, R2 is included in the most recent update for Microsoft Dynamics GP 2013.

4. The update must be installed at all servers and workstations that have a Microsoft Dynamics GP installation otherwise a version error will occur when launching Microsoft Dynamics GP.

5.  If you are currently using Business Portal for Microsoft Dynamics GP 6.0 and utilize the Human Resource Self Service Suite, you need to install the Business Portal hotfix on the Business Portal server.  This will correct issues that you would otherwise encounter in the Human Resource Self Service Suite in Business Portal due to related to table changes that were made in Microsoft Dynamics GP 2013 Service Pack 2 around Payroll Direct Deposit. Here is a link to the blog that covers this information:

Microsoft Dynamics GP 2013 Service Pack 2 does not seem to play NICE with Business Portal Human Resource Self Service Suite 6.0
https://community.dynamics.com/gp/b/dynamicsgp/archive/2013/11/05/microsoft-dynamics-gp-2013-service-pack-2-does-not-seem-to-play-nice-with-business-portal-human-resource-self-service-suite-6-0.aspx?WT.mc_id=BlogPost

Pre-Install and Upgrade Tips

1. Backup the DYNAMICS database and all company databases prior to installing the year-end update.

2. Export all modified reports and forms to package files.   (Microsoft Dynamics GP | Tools | Customize | Customization Maintenance).

3. Make a backup copy of the modified reports and forms .DIC files.  Refer to the Dynamics.set file for the path to the modified .DIC files.

4. Ensure that you have a working backup of any eConnect PRE and POST Procedures if they are customized.

5. Configure a test environment to test the upgrade prior to installing in the live environment. 
**It is highly recommended to test the year-end update first in a test environment.**

 Install and Upgrade Tips 
  
1. The user running the MSP update must have local admin rights on the workstation or server operating system.

2. When installing the update at the first machine, there are two components to the installation: a. Upgrade the application install b. Upgrade DYNAMICS and all company databases and all modified reports and forms in Microsoft Dynamics GP Utilities

3. Typically, the update is installed at the SQL Server first to upgrade the databases in Microsoft Dynamics GP Utilities. If a Microsoft Dynamics GP installation does not exist at the SQL Server, the databases can be updated from the first client workstation or Terminal Server.

4. Verify the Microsoft Dynamics GP installation used to upgrade the databases includes all additional product installations.  For example, if Project Accounting is used, verify that Project Accounting is installed at the machine where running Microsoft Dynamics GP Utilities for the database upgrade.

5. If the installation of the MSP fails, refer to the Windows Installer Log or Windows Event Viewer for more information. Refer to KB 2545723 for steps to create a Windows Installer Log.

KB 2545723 - How to Capture a Windows Installer Log
http://support.microsoft.com/kb/2545723

6. Open the Windows Installer Log in a text editor and search for “Return Value 3” to find the failure location in the log.

7. If the installation of the MSP fails, try installing via the command line. Refer to KB 912997 #13 for steps.

KB 912997 - Frequently Asked Questions about the Windows Install MSP files for Microsoft Dynamics GP
http://support.microsoft.com/kb/912997

8. Enable a Dexsql.log prior to upgrading the databases in Utilities. If an error occurs during the database upgrade, the Dexsql.log can be used to troubleshoot the issue.  Refer to KB 850996 for steps.

KB 850996 - How to Enable a Dexsql.log
http://support.microsoft.com/kb/850996

9. If the database upgrade fails, do not restore the databases as all troubleshooting can take place at the point of failure.

10. If a red X appears next to the company name in the Update Company window, the table conversion failed. Refer to the Support Information Section of the Upgrade Hot Topic for troubleshooting steps.

Upgrading to Microsoft Dynamics GP 2013
https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOT_TOPIC_MDGP2013Upgrade

Microsoft Dynamics GP 2010 Upgrade Hot Topic
https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOTTOPIC_MDGP2010_Update
 

11. All modified reports and form dictionaries must be upgraded using the Update Modified Forms and Reports process at the Additional Tasks window in Microsoft Dynamics GP Utilities.

12. If all modified reports and form dictionaries are shared, only upgrade the dictionaries once.

13. The MSP file can be pushed out to client workstations using Automatic Client Update, Group Policy or other mass deployment tools.

Post-Install and Upgrade Tips


1. Backup the DYNAMICS database and all company databases following the upgrade.

2. Export all modified reports and forms to package files following the upgrade. (Microsoft Dynamics GP | Tools | Customize | Customization Maintenance).

Assistance for the Year-End Install and Upgrade 


1. Microsoft Dynamics GP Support and Services Blog
https://community.dynamics.com/product/gp/gptechnical/b/dynamicsgp/default.aspx

2. Microsoft Dynamics Community
https://community.dynamics.com/GP/default.aspx


3. Microsoft Dynamics Support
https://mbs.microsoft.com/support/newstart.aspx

If you are creating a case with the Technical Support Team, please refer to the routing below to ensure you are routed to the correct Professional for assistance.

1. Assistance with the install of the MSP
a. Support Topic Selection: System and Security Setup, Installation, Upgrade and Migrations
b. Sub-topic Selection: System Installation

2. Assistance with the database or report/form upgrade in Microsoft Dynamics GP Utilities
a. Support Topic Selection: System and Security Setup, Installation, Upgrade and Migrations
b. Sub-topic Selection: System Upgrade

3. Assistance with installing the tax table update in Microsoft Dynamics GP
a. Support Topic Selection: Payroll
b. Sub-topic Selection: Payroll Tax Update

4. Assistance with Payroll-specific issues related to the Year-End release and procedures
a. Support Topic Selection: Payroll
b. Sub-topic Selection: Year-End Procedures

KnowledgeBase Articles and Resources 
 
1. 2014 U.S. Payroll Year-End Update for Microsoft Dynamics GP 2013 Download Page
https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/usgpye2013

2. 2014 U.S. Payroll Year-End Update for Microsoft Dynamics GP 2010 Download Page
https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/usgpye2010

 
3. Microsoft Dynamics GP 2013 Upgrade Hot Topic
https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOT_TOPIC_MDGP2013Upgrade 
  
4. Microsoft Dynamics GP 2010 Upgrade Hot Topic
https://mbs.microsoft.com/customersource/northamerica/GP/support/hot-topics/HOTTOPIC_MDGP2010_Update
 

5. Service Packs and Hotfixes for Business Portal 6.0 for Microsoft Dynamics GP 2013
https://mbs.microsoft.com/customersource/northamerica/GP/downloads/service-packs/MDGP2013_BP60_patchreleases

6. KB 2545723 - How to Capture a Windows Installer Log
http://support.microsoft.com/kb/2545723

7. KB 912997 - Frequently Asked Questions about the Windows Install MSP files for Microsoft Dynamics GP
http://support.microsoft.com/kb/912997

8. KB 850996 - How to Enable a Dexsql.log
http://support.microsoft.com/kb/850996

Thanks!
Sarah

Hi everyone,

With the upcoming release of the 2014 Year End Update for Microsoft Dynamics GP, we wanted to get all of our table and column changes in one place.  If any changes are made after this is posted, we will update this blog with the cumulative changes.

So far, the changes to report are based around the new Affordable Care Act features, so will be applicable to Microsoft Dynamics GP 2013 and Microsoft Dynamics GP 2015 versions.

New Tables

UPR40105-   upr1095Setup 

UPR00904 - uprMstrDependentACA

UPR00905 - uprMstrEmployeeACA 

UPR10108 - uprYearEndDependentACAHistory 

UPR10109 -  uprYearEndEmployeeACAHistory 

Existing Table Changes for GP2013

BE010130 -     HR - HR_Benefit_MSTR

- OfferOfCoverageCode
- SafeHarborCode

BE020230    - HR_Benefit_SETP

- OfferOfCoverageCode
- SafeHarborCode

UPR10100 - UPR_Year_End_WORK_HDR

- PHONE1 

I hope this information will be helpful to you.  More information on the Affordable Care Act will be published in a separate blog next week.

Thanks,

Dan | Microsoft Dynamics GP Systems Support

Hi Everyone!

Below you will find some tips to help ensure that your Payables Management Year End Close process goes smoothly for you!

When should the Year End Close for Payables Management be done?

1. The Calendar Year End Close Routine should be run at the end of the Calendar year prior to posting transaction in the next Calendar year.

2. The Fiscal Year End Close Routine should be run at the end of the Fiscal year prior to posting transactions in the next Fiscal year.

What does the Year End Close Process do and /or affect?

1. The Calendar year end close process transfers the 1099 Amount from the Year to Date column to the Last Year column in the Amounts Since Last Close view in the Vendor Yearly Summary window, found under (Cards – Purchasing – Summary – Yearly Button).

2. The Fiscal year end close process transfers all other amounts from the Year to Date column to the Last Year column in the Amounts Since Last Close view, also found under (Cards – Purchasing – Summary – Yearly Button).

*If the Year to Date or Last Year amounts are incorrect in the Amount Since Last Close View contact support for scripts that can be ran to correct these amounts.

3. When these amounts are transferred this will also affect SmartList amounts that contain Year to Date or Last Year summary columns.

4. The Vendor Summary report will also be affected by the transfer of amounts from the Year to Date column to the Last Year column when closing the year.

What steps should I take to close the year?

1.      Post all transactions for the current year.

2.      Make sure that transactions for the new year are saved, not posted. 

3.      After verifying those steps, make a backup of your company database.

4.      Follow the steps in KB 875169: “Year-end closing procedures for the Payables Management module in Microsoft Dynamics GP”.

What changes should I know about related to the Year End Update for Payables Management?

1.      The 1099 MISC form had the names blanked out for boxes 11 and 12.

2.      The following changes were made to the format for the 1099 INT form: 

• Added Box 10 - Market Discount
• Added Box 11 - Bond Premium
• Renamed Box 13 - Box 15 - State tax withheld

Key points to remember:

1. Follow the steps outlined in KB 875169 and always make a restorable backup before starting any year-end close procedure.

2. Payables Management is not fully date sensitive. In the Vendor Yearly Summary window, the Summary Views for Calendar Year and Fiscal Year are date sensitive, so will be correct.  However, the Amounts Since Last Close view will move amounts from the Year to Date Column to the Last Year column at the point in time you ran the Year End close process for Payables Management.   So it is still recommended that you process your year-end closing routines at the actual year end, and before you post any transactions in the new year so this view is correct.

3. Vendors should be marked as 1099-able before any transactions are posted for them so that 1099 information is updated automatically throughout the year.  In Microsoft Dynamics GP 2010, refer to KB 918536 to correct vendors that were not marked correctly.  However, there is new functionality in Microsoft Dynamics GP 2013 that you will want to utilize to make editing 1099 information (by vendor and/or by transaction) much easier.          

4. Please note that both Payables Management and Receivables Management Year End KB article’s say to close the tax year. This will only need to be done once, after both Receivables and Payables are closed. (The reason that we list this on both KB Articles is because some users may not use both Payables Management and Receivables Management.)

5.  I would recommend watching the Readiness videos for Microsoft Dynamics GP 2013 so you can utilize all the great new features for printing, editing and other maintenance for 1099 forms.  (The link is provided below in the Resources section.)

Assistance for Payables Management Year End Close

Microsoft Dynamics GP Blog - http://blogs.msdn.com/b/dynamicsgp/
Microsoft Dynamics Community - https://community.dynamics.com/product/GP/default.aspx
Microsoft Dynamics Support - https://mbs.microsoft.com/support/newstart.aspx

If you are creating a case with the Technical Support Team, please refer to the routing below to ensure you are routed to the correct Professional for assistance.

Assistance with the Payables Management Year End Close
--Support Topic Selection: Financial - Payables Management
---Sub-topic Selection: Period / Year End Close

Resources:

Year-end closing procedures for the Payables Management module in Microsoft Dynamics GP are found in KB 875169:  http://support.microsoft.com/kb/875169

The Year-End slide deck and the What's New for Year-End video should be complete soon and the link will be included on future blog articles.   

Be sure to check back to the Year-End Schedule post for current posted blogs and upcoming blog posts related to Year-End Closing for Dynamics GP:

Good luck and have a great Year-End!

Shannon Aune | Microsoft Dynamics GP Support  | Sr. Technical Support Engineer

Hi everyone,

Yes, it's time to start planning for Year-End again!  I'd like to provide you with information to help ensure that your U.S. Payroll Year End goes smoothly.

In Support, we are often asked "if it is okay to install the 2014 Year End Update even though 2014 payrolls are not completely processed?" The answer to that is YES YOU CAN!  Please review all documentation in detail so that you are well prepared for the year-end close, and knowledgeable about what has changed for this year.

What versions of Microsoft Dynamics GP will be supported with the 2014 Year End Update?

     • Microsoft Dynamics GP 2010   *This will be the LAST year that a Year End update is available.  Click HERE for more information on the lifecycle for Microsoft Dynamics GP 2010.

     • Microsoft Dynamics GP 2013 - (This does include Microsoft Dynamics GP 2013 R2)

     • Microsoft Dynamics GP 2015  - (YEC update to release January 15 ,2015) 

     • Note:  The Year-end/Tax Update is inclusive of all previous hot fixes, services packs and year-end downloads.

What are the target release dates?

• The 2014 Year End Update for Microsoft Dynamics GP 2010 and Microsoft Dynamics GP 2013 are targeted to release by the end of November. (This will be updated when it is available.)

• The 2014 Year End Update for Microsoft Dynamics GP 2015 is targeted for January 15 release.

• The 2015 Round 1 Tax Update (tax table update only) for Microsoft Dynamics GP 2010 and Microsoft Dynamics GP 2013 will be available the week of December 19th, 2014.   This update will increase the FICA Social Security Limit to the new 2015 calendar year amount.  *NOTE: Therefore, do not install this tax update until the 2014 Year End Wage file is created and ALL pay runs for the 2014 year are completed!

• The 2015 Round 2 Tax Update will be available mid-January.

When should the Year End Close be performed?

The Payroll Year End Close should be processed after all pay runs have been completed in the current year, and before processing any pay runs in the New Year.

Are there any changes I should know about related to the Year End Update for Payroll?

• There are NO W2 form changes

• There are W3 form changes

• There are EFW2 (Electronic Filing) changes. *The file will error if these changes are not incorporated.

• 1099-R (Retirement) distribution code changes

• Affordable Care Act changes - available in Microsoft Dynamics GP 2013 and higher versions only

• Product Quality Fixes around Payroll Year-End

Where can I learn more about the Affordable Care Act (ACA) changes?

• Another blog will be released tomorrow to further discuss the Affordable Care Act changes in Microsoft Dynamics GP and will include Frequently Asked Questions.

• For more information on the table/column changes due to the Affordable Care Act, click HERE.

• For more information on the Affordable Care Act, click HERE to read Terry's preliminary blog.

What does the Year End Close (YEC) process do?

The YEC process creates the 'Year End Wage' file with annual wage information used to generate W2s, W3s, 1099-R's, and the W2 Electronic file for the year being closed.

What steps should I take to close the year? (See KB Article 850663 for detailed instructions on each step listed below):

**First and foremost make a restorable backup of the company database so you can restore should you run into a problem.**

1.  Verify that you have installed the latest 2014 payroll tax updates. The 'Last Tax Update' should read 12/17/2013 or later in the Payroll Tax Setup Window (Microsoft Dynamics GP >> Tools >> Setup >> System >> Payroll Tax).   (Verifying that the Last Tax Update is dated greater than the Round 1 tax update for 2014 will ensure you have the correct FICA limit in place when you create the Year-End Wage file.)

2.  Complete all pay runs for the current year. 

3.  (Optional) Complete all month-end, period-end, or quarter-end procedures for the current year. 

4.  Make a backup of the original file.

5.  Install the Year-End Update. 

6.  Create the Year-End file. 

7.  Make a backup of the new file. 

8.  Verify W-2 and 1099-R statement information. 

9.  Print the W-2 statements and the W-3 Transmittal form. 

10. Print the 1099-R forms and the 1096 Transmittal form. 

11. (Optional:) Create the W-2 Electronic file. 

12. (Optional:) Archive inactive employee Human Resources information. 

13. Set up fiscal periods for 2015. 

14. (Optional:) Close fiscal periods for the payroll series for 2014. 

15. Install the payroll tax update for 2015. 

To recap, prior to processing a pay run in 2015 the following is:

Required:

• All 2014 pay runs completed.

• Year End Wage File created.

• Backup of company database made.

• Payroll Tax Update for 2015 (2015 Tax Update Round 1) installed.

Optional:

• Print W-2s.

• Create W-2 Electronic File.

Can we run a payroll in the new year prior to closing the 2014 year?

If you must process a payroll for the new year before the 2014 year-end closing procedures are completed, refer to the 'Alternative Payroll Year End Checklist' steps in KB 850663. 

Why may those using Microsoft Dynamics GP 2010 want to upgrade?

The functionality needed to track the Affordable Care Act changes for calendar year 2015 is included in the Year-End Update for Microsoft Dynamics GP 2013 and higher versions.  If assistance is needed for the install or upgrade, click HERE.

ASSISTANCE: Here are some links to use if you need assistance for Payroll Year End Close

• Refer the landing page for the 2014 Year-End Blog Series.

• Microsoft Dynamics GP Blog - https://community.dynamics.com/product/gp/gptechnical/b/dynamicsgp/default.aspx

• Microsoft Dynamics Community - https://community.dynamics.com/default.aspx

• Microsoft Dynamics Support - https://mbs2.microsoft.com/Support/newstart.aspx

   If you are creating a case with the Technical Support Team for assistance with Year End close for Payroll, please refer to the category selections below to ensure you are routed to the correct Support team for assistance:

     --Support Topic Selection:    Payroll

          --Sub-topic Selection:      Year End Procedures 

RESOURCES:

•Year-end closing procedures for the Payroll module in Microsoft Dynamics GP are found in KB 850663:  http://support.microsoft.com/kb/850663

•Be sure to check back to the Year-End Blog Schedule for current posted blogs and upcoming blog posts related to Year-End Closing for Dynamics GP.

YEAR-END UPDATE LINKS:  Here are the 2013 Year-End Update pages which will provide you with documentation and installation instructions:

2014 U.S. Payroll Year End Update for Microsoft Dynamics GP 2013 Download Pages:

https://mbs.microsoft.com/partnersource/northamerica/deployment/downloads/tax-regulatory-updates/usgpye2013

https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/usgpye2013

2014 U.S. Payroll Year End Update for Microsoft Dynamics GP 2010 Download Pages:

https://mbs.microsoft.com/partnersource/northamerica/deployment/downloads/tax-regulatory-updates/usgpye2010

 https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/usgpye2010

TAX UPDATE LINKS:  Use these links to access the latest (and previous) Tax Updates:

Latest U.S. Payroll Tax Update for Microsoft Dynamics GP2013:

https://mbs.microsoft.com/partnersource/northamerica/deployment/downloads/tax-regulatory-updates/TUGP2013

https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/TUGP2013

Latest U.S. Payroll Tax Update for Microsoft Dynamics GP 2010:

https://mbs.microsoft.com/partnersource/northamerica/deployment/downloads/tax-regulatory-updates/TUGP2010

https://mbs.microsoft.com/customersource/northamerica/GP/downloads/tax-regulatory-updates/TUGP2010

I hope you find this information helpful!  Please watch for more blogs and helpful information to come.   Have a great Year End!!!

Cheryl Waswick | Microsoft Dynamics GP  | Senior Support Engineer

It’s that time of year again, Year End is right around the corner, and the Affordable Care Act is on everyone's mind!!

In this blog, I’d like to provide you with information regarding Affordable Care Act changes included in the 2014 Year End Update; give you an idea of what you can expect to see in future code releases throughout the upcoming year; and provide you with answers to FAQs regarding ACA and Microsoft Dynamics GP.

First, let’s cover the basics:

With mandatory reporting required for the Affordable Care Act at the end of the 2015 year, we wanted to lay the foundation for this as soon as possible. We've begun by implementing ACA tracking mechanisms with the 2014 Year End Update. In addition, changes we make throughout the year will ensure you'll be able to successfully generate the 1094-C and 1095-C forms at the end of 2015. The 1094-C and 1095-C forms will be included in Quarter 1 of 2015.

Affordable Care Act (ACA) changes will be implemented and supported for the following versions:

Microsoft Dynamics GP 2013, and beyond

Affordable Care Act (ACA) changes will not be implemented or supported for the following versions:

Microsoft Dynamics GP 2010, or previous versions

If you are currently on Microsoft Dynamics GP 2010 you may want to consider upgrading soon.  Mainstream support (ie. tax updates) will end on 10/13/2015.  Extended support with no updates will end on 10/13/2020. Please refer to the Support Life Cycle for Microsoft Dynamics GP 2010.

 Note: No changes were made to Business Portal Benefit Self Service or Human Resource Management Self Service for ACA.

Requirements to Implement Changes Associated with the Affordable Care Act:

In addition to Payroll, the Human Resources module is required to track Affordable Care Act information in Microsoft Dynamics GP.

The GREAT news is that Human Resources is FREE with Microsoft Dynamics GP 2013 and beyond!

Recommended to Track ACA Information:

• Install the 2014 Year End Update
• Install Human Resources
• Install Human Resources and Payroll Suite to utilize Deductions In Arrears (DIA)
  
  • Deductions In Arrears allows you to track uncollected deductions to ensure they are recovered in a future pay run.
    

• Add all Employee Dependents
• Ensure Benefits and Deductions exist both in Human Resources and Payroll (Integration between HR and PR complete)

Affordable Care Act changes included in the 2014 Year End Update:

Changes to Windows:

Health Insurance Setup Window
The Offer Of Coverage Code (line 14) and Safe Harbor Code (line 16) fields were added to accommodate ACA changes implemented with the 2014 Year End Update in the Health Insurance Setup window. To open the Health Insurance Setup window, click the HR and Payroll series button, click Human Resources on the Setup content pane, click Benefits and Deductions and then click Health Insurance:

The codes you assign in this window will be stored in the BE020230 - HR Benefit Setup table. Users can ‘roll down’ changes made here to the Health Insurance Enrollment Window to update the employee level if desired.

Health Insurance Enrollment Window
The Offer Of Coverage Code (line 14) and Safe Harbor Code (line 16) fields were added to accommodate ACA changes implemented with the 2014 Year End Update in the Health Insurance Enrollment window. To open the Health Insurance Enrollment window, click the HR and Payroll series button, click Human Resources on the Cards content pane, click Employee -Benefits and then click Health Insurance:

       
Users can assign appropriate Affordable Care codes in this window, or code changes can be ‘rolled down’ from the Health Insurance Setup window.  ACA codes in this window (Offer Of Coverage Code and Safe Harbor Code) are be stored in the BE010130 - HR Benefit Master table.

Employee Dependents Window
The Health Insurance Coverage field was added accommodate ACA changes implemented with the 2014 Year End Update in the Employee Dependents window. To open the Employee Dependents window, click the HR and Payroll series button, click Human Resources on the Cards content pane, click Employee, and then click Dependents:

Things to know about this window:

• Dependents in this window will default to ‘covered’.
• If the dependent is not covered, you will need to change the ‘Health Ins. Coverage’ to ‘not covered’ in this window. Dependent coverage information is stored in the UPR00904 table and can be updated throughout the year.
• Dependent coverage data in the UPR00904 is not updated retroactively. As such, if the dependent is entered into the system on 03/15/2014: the UPR00904 will store records for that dependent starting in March of 2014 and going forward.

New Windows:

Affordable Care Act Codes windows
The Affordable Care Act Codes window was added to accommodate ACA changes implemented with the 2014 Year End Update. The Affordable Care Act Codes window can be opened by clicking on the Lookup buttons in the Health Insurance Setup window or in the Health Insurance Enrollment window:

The Affordable Care Act Codes window contains a list of available (pre-determined) codes for line 14 and line 16. Data for this window is stored in the UPR40105 table.

Changes to Existing GP Tables:

BE020230 - HR Benefit Setup table (HR_Benefit_SETP) had the following fields added:

•     OfferOfCoverageCode
•     SafeHarborCode

BE010130 - HR Benefit Master table ( aka HR_Benefit_MSTR) had the following fields added:

•     OfferOfCoverageCode
•     SafeHarborCode

New Tables:

UPR40105 - UPR 1095 Setup File

The UPR40105 holds ACA codes and descriptions. You can see the data stored in this table when you open the Affordable Care Act Codes window.

This table is utilized to allow users to fill out boxes that will show on the Federal Government’s 1095 form.

UPR00904 – Payroll Master Dependent ACA

The UPR00904 table stores a record for every dependent associated with each employee.

Things to know about this table:

• Health Insurance Dependent Coverage (HealthInsDependentCov) field meaning:
  • 1 = Covered
  • 2 = Not Covered
• Dependents are marked as ‘covered’ in this table by default
• This information can be updated throughout the year, and is tracked on a monthly basis

UPR00905 – Payroll Master Employee ACA

The UPR00905 table stores Affordable Care Act Codes assigned in the Health Insurance Enrollment window.

• ACA Codes can be updated in the Health Insurance Enrollment window.
• These codes are tracked monthly throughout the year.

UPR10108 – Payroll Master Dependent ACA History and UPR10109 - Payroll Master Employee ACA History tables

While these tables were added with the 2014 Year End Release, they are not currently being used. Code will be added to populate these tables with an upcoming release.

• The UPR10108 will be updated during the year-end close is process in Payroll using data from the UPR00904 (Payroll Master Dependent ACA) table.  
• The UPR10109 will be updated during the year-end close is process in Payroll using data from the UPR00905 (Payroll Master Employee ACA) table.  

Expected to be included in a future release this year (2015):

The 1095-C (given to employee from the employer - like a W2- to show Employer Provided Health Insurance Offer and Coverage) and 1094-C (summary the employer fills out of all employees that received the 1095-C) forms will be added in Quarter 1 of 2015.

When you create the Year End Wage File for the 2015 year, all Affordable Care Act information you've been tracking will be accumulated to the year end tables, similar to how we accumulate the W2 information. 

Just like the W2:

• You can edit 1095-C information if needed.
• Edits will lost if the Year End Wage File is removed and recreated.

Upcoming Windows:

 
Edit 1095-C Covered Individuals and Edit 1095-C Information windows (to be included in future release)
The Edit 1095-C Covered Individuals and the Edit 1095-C windows will be added to accommodate ACA.

• You will be able to open the Edit 1095-C Covered Individuals window by clicking on the HR and Payroll series button, click Edit W-2s on the Routines content pane, and then click the Dependents button.
• You will be able to access the Edit 1095-C window by clicking on the HR and Payroll series button, click Edit W-2s on the Routines content pane, and then click the 1095-C button.

Note: The Dependents and the 1095-C buttons are greyed out in the Edit W-2 window after you install the 2014 Year End Update. This is because the new windows will be added in a future release:

• Information in the upcoming Edit 1095-C Covered Individuals window will be stored in the UPR10108 table.
• Information in the upcoming Edit 1095-C Information window will be stored in the UPR10109 table.

Human Resource Setups You Should be Aware of:

Payroll View for Human Resources in User Setup Window

It is important to mark the box next to Payroll View for Human Resources in the User Setup window. To open the User Setup window, click the Administration series button and then click User on the Setup content pane:

• If Payroll View for Human Resources is selected, a message will prompt the user to set up corresponding benefit/deduction codes in Payroll to complete the integration between HR and Payroll when a user creates a benefit or deduction in HR.
• If Payroll View for Human Resources is not selected, the benefit enrollment will be incomplete. As such, users need use the Reconcile Human Resources window to update the benefit definitions appropriately.

Automatically Update Payroll Benefits & Deductions in Benefit Preferences Setup Window

Consider unchecking the box next to Automatically Update Payroll Benefits & Deductions until you are familiar with setting up benefits and deductions in HR to ensure they flow appropriately into PR.
To open the Benefit Preferences window, click the HR and Payroll series button, click Human Resources on the Setup content pane, click Benefits and Deductions and then click Benefit Preferences:

Marking the box next to Automatically Update Payroll Benefits & Deductions will update payroll benefit and deductions records without displaying integration messages.

Note: If you are unsure whether or not the HR benefit/deduction has all pertinent data entered to integrate successfully: I recommend you leave this box unmarked. When this box is unmarked, you will able to watch the flow from HR to PR, and this will reduce the chances of failed HR to PR integrations.

Frequently Asked Questions:

Question 1:
What is the best way to setup benefit and deduction codes to facilitate ACA reporting to ensure we can break out the cost of the benefit from the cost to the employee?
Answer 1:
Please refer to Terry’s blog Guidelines for Payroll W-2 Benefit Reporting that describes steps you can take to ensure successful reporting on benefits and deductions.
Question 2:
We’ve never used HR in the past. How can we ensure that all of our benefits and deductions are integrated successfully between Human Resources and Payroll?
Answer 2:
If you are implementing HR for the first time, it will be necessary to process ‘Reconcile’ Routine in Human Resources to ‘Update Benefit Setups’ and ‘Update Benefit Enrollments’.  

Click HEREfor a detailed document that walks you through the steps needed to process ‘Reconcile’ Routine in Human Resources to ‘Update Benefit Setups’ and ‘Update Benefit Enrollments’. 

Question 3:
I don't want to install Human Resources. Is there any way to track ACA information in Payroll only?
Answer 3:
Human Resources must be installed to utilize Affordable Care Act functionality. Again, the GREAT news is that Human Resources is FREE in Microsoft Dynamics GP 2013 and beyond.

Question 4:
What if I don't upgrade right away?
Answer 4:

If you aren't able to install the 2014 Year End Update right away, never fear! We've got you covered! You can utilize the Edit 1095-C and the Edit 1095-C Covered Individuals windows to record ACA information from prior to when you upgraded.

Microsoft Dynamics GP will not retroactively update ACA tracking. It will track ACA information going forward only.

Question 5:

Where can I track 'Lowest Coverage Offered' in GP?

Answer 5:

With the release of the 2014 Year End Update, there is no tracking available for 'Lowest Coverage Offered'. Development haven't yet determined how or where this will be tracked. As soon as we've decided on this, you'll be the first to know!!

Question 6:

Can I submit my 1095-C's and 1094-C electronically in Microsoft Dynamics GP?

Answer 6:

Currently, ACA Electronic Filing is not scheduled to be implemented in Microsoft Dynamics GP in the upcoming year.

Question 7:

Can I track employee hours worked in Microsoft Dynamics GP?

Answer:

Yes, you can! Click HERE, and view the video in Terry's blog, "Affordable Healthcare Act, are you prepared and are you using Microsoft Dynamics GP to its full potential?" The video is full of great suggestions around how to utilize Microsoft Dynamics GP to track employee hours!

Additional Resources:

Assistance for Affordable Healthcare Act Questions

Microsoft Dynamics GP Blog -https://community.dynamics.com/product/gp/gptechnical/b/dynamicsgp/default.aspx

Microsoft Dynamics Community - https://community.dynamics.com/default.aspx

Microsoft Dynamics Support - https://mbs.microsoft.com/support/newstart.aspx

If you are creating a case with the Technical Support Team for assistance with questions regarding the Affordable Care Act in GP please refer to the category selection below to ensure you are routed to the correct Support team for assistance:

     --Support Topic Selection:    Human Resources or Payroll (depending on the question)

Helpful Links:

• Click HERE to view Terry's AWESOME blog around the Affordable Care Act.

• Click HERE to view Affordable Care Act Tax Provisions Questions and Answers from the IRS.

• Click HEREto view Questions and Answers on Employer Shared Responsibility Provisions Under the Affordable Care Act provided by the IRS.

• ClickHERE for U.S. Payroll Year End Update for Microsoft Dynamics GP 2013.

• Click HERE for U.S. Payroll Year End Update for Microsoft Dynamics GP 2010.

**Be sure to check the Year-End Schedule post for current posted blogs and upcoming blog posts related to Year-End Closing for Dynamics GP.

Wishing you a seamless and successful Year End!!

Andrea Melroe | Technical Advisor | Microsoft Dynamics GP Support

The end of 2014 is almost here, so let's discuss closing the year in Fixed Assets!  I'd like to provide you with information pertaining to what's new with the Year End Update, what the year end process does, as well as when it should be completed in Fixed Assets.  Good luck!

Changes with the release of the 2014 Year End Update you should be aware of in Fixed Assets:

Luxury Auto Maximum Depreciation Deduction Amounts: The maximum depreciation deduction amounts allowed for luxury vehicles has been updated for assets placed in service in calendar year 2014 to comply with IRS Guidelines:

Things to keep in mind when closing the year in Fixed Assets:

• When you close the year in Fixed Assets, you have to do it for each book you have setup.
• All books must be closed before you process depreciation for the new year. 
• We recommend you close the Fixed Assets year after you close the year in Payables Management but before you close the General Ledger year.

 When you close the year in Fixed Assets, the following fields are updated:    

•Asset General Window:

• The YTD Maintenance amount is cleared from the Expand last Maintenance Date Window.
• The Quantity is copied to the Begin Quantity field in the Expand Quantity Window.

•Asset Book Window:

• The YTD Depreciation Amount is cleared.
• Cost Basis is copied to Begin Year Cost field.
• Life to Date Depreciation is copied to Begin Reserve field.
• Salvage Value is copied to Begin Salvage field.

•Book Setup Window:

• The Current Fiscal Year is incremented to the next year.

Steps to complete the year end close process in Fixed Assets:

1. Print all the reports that you will need for the year that you are closing before closing the year.
2. **Make a backup!**
3. Follow the steps in KB865653: “The year-end closing procedures for the Fixed Asset Management module in Microsoft Dynamics GP”.
4. You must process depreciation to the last day of the year that you are closing before you close the year.

• • • In Microsoft Dynamics GP 2010 and prior versions: The last day of the Fixed Assets year can be confirmed by navigating  Microsoft Dynamics GP>> Tools >> Utilities >> Fixed Assets >> Build Calendar >> Inquire.
    • In Microsoft Dynamics GP 2013 and future versions:  The last day of the Fixed Assets year can be confirmed by navigation to Microsoft Dynamics GP>>Tools>>Setup>>Fixed Assets>>Calendar.

MICROSOFT DYNAMICS GP - FEATURES

• Microsoft Dynamics GP 2015 (Soon to be released)

With the upcoming release of Microsoft Dynamics GP 2015, I wanted to let you know that we’ve added an optional report to the Fixed Assets year end closing routine.  Now, in a single step, you can close your year and print a status report of all the assets that are being affected by the close.  On the report you’ll see the year to date depreciation, cost basis, accumulated depreciation, net book value and more.

REMINDER FOR MICROSOFT DYNAMICS GP 2010 USERS:

For Microsoft Dynamics GP 2010 and prior versions, DO NOT manually change the year in the Book Setup window so you can run depreciation for the next year before closing the current year.  If you do this, you will encounter problems at the end of the next year.  This is because Fixed Assets compares the Yearly Depreciation Amount field to the YTD Depreciation field.  If you run depreciation for the next year by changing your fiscal year in Book Setup, when you close the current year the YTD Depreciation amount is set back to $0.00.  This includes the amount of depreciation that you calculated for the new year.  As you complete depreciation for the new year, the YTD field will be updated but the amount that was generated for the first month (or months) before the previous year was closed is not included in that YTD total.  When you get to the last period, the depreciation amount will be doubled.  The GP code and procedures will determine that not enough depreciation was taken through the year because the Yearly Depreciation Amount does not equal the YTD amount due to the first month (or months) not being included in the YTD figure.  

Assistance for Fixed Assets Year End Close:

•Microsoft Dynamics GP Blog - https://community.dynamics.com/product/gp/gptechnical/b/dynamicsgp/default.aspx

•Microsoft Dynamics Community - https://community.dynamics.com/default.aspx

•Microsoft Dynamics Support - https://mbs.microsoft.com/support/newstart.aspx

If you are creating a case with the Technical Support Team, please refer to the routing below to ensure you are routed to the correct Professional for assistance:  

Support Topic Selection:  Financial – Fixed Assets

Sub-topic Selection:  Year End Procedures

Resources:

Year-end closing procedures for the Fixed Assets module in Microsoft Dynamics GP: http://support.microsoft.com/kb/865653

Be sure to check back to the Year-End Schedule post for current posted blogs and upcoming blog posts related to Year-End Closing for Dynamics GP.

Have a great Year-End!

Adam Gaber | Microsoft Dynamics GP  | Senior Support Engineer